Skip to content
Back to milestones

OpenShell 0.1.0

New issue
Open
Due by September 15, 2026
•Last updated Aug 28, 2026

What’s in the release: 0.1.0 removes the alpha designation and introduces a predictable release cadence with a clear API change policy. It deprecates legacy APIs, supports reliable cross-version upgrades of sandboxes and services, and is suitable for production workloads.

Release Cadence

  • Stable releases are cut weekly and tested against a list of supported OpenShell configurations.
  • Each stable release goes through automated release qualification that includes conformance testing, upgrade testing, checks for breaking api changes, and security testing.
  • Patch releases are backwards compatible. Minor releases may contain breaking changes.
  • Security updates are back ported N-1 minor releases.

API Change Policy

  • APIs are stable by default and explicitly marked as experimental if we expect them to change often
    • Stable APIs may change with notice and a migration guide between minor releases
    • Experimental APIs may change without notice between patch releases

Full details are in RFC-0014, https://github.com/NVIDIA/OpenShell/tree/main/rfc/0014-release-stability.

The following APIs and contracts will adhere to the new API change policy

  • Sandbox APIs
  • Providers (v2 is now the canonical Provider API)
  • Policy Configuration
  • Workspace APIs
  • Extension Interfaces: Drivers, Interceptors, Middleware
  • TOML Gateway Config
  • Helm Chart

Deprecated API & Features

  • Providers v1 (providers v2 become the canonical provider version)
  • Inference APIs (replace by Providers)
  • Community images and associated repo

As part of 0.1.0 we’ll apply the breaking API changes proposed in NVIDIA/OpenShell#2565. Once these changes are in place, the APIs will adhere to the API changed guidelines outlined above.

52% complete

List view

0 issues of 19 selected