Skip to main content

v0.2.0

Released September 2, 2026. Supported until March 2, 2027.

v0.2.0 ships 1 breaking change, 2 security updates, 8 new features, and 15 bug fixes. The release contains a breaking change, and operator action is required before upgrading. Behavior between the management plane and the data plane changed in this release. The most severe security issue cleared is high.

Upgrade and rollback​

  • Breaking change: operator action is required before upgrading. See the warning below.
  • The upgrade rolls through without dropping traffic.
  • Rollback to v0.1.5 is unconditional.
Action required before upgrading

Provider creation through the catalog API changed. UpsertProvider previously asserted "enabled" on every write; a provider created without is_enabled now arrives disabled, and registering a model under it is refused with FailedPrecondition until the provider is enabled. Scripts that create providers must pass is_enabled explicitly. Existing providers are unaffected, and enabling an already created provider is a single further call.

The per-entry change list for this release predates the release notes pipeline. Change lists are published from v0.2.1 onward.