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.
A fully detailed version of these release notes (including artifact versions) is included in the Admin Console.
Click here to learn how to bring up the full release notes.
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.
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.
Known issues
Gateway
A budget on a single API key does not survive a rotation of that key. The budget stays bound to the retired credential, so the replacement key runs with no budget while the policy still lists as active, and nothing warns that enforcement has stopped. On this release a key budget is unreliable on any credential with a rotation schedule, and the interim options are described under budget cap limitations and workarounds. Fixed in v0.3.0, where a key budget binds to the client behind the key and follows the rotation to the replacement key.