v0.1.5
Released August 28, 2026. Supported until February 28, 2027.
v0.1.5 ships 1 breaking change, 11 security updates, 27 new features, 102 bug fixes, and 1 deprecation. 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
- The release carries a breaking change, but no operator action is required before upgrading.
- The upgrade rolls through without dropping traffic.
- Rollback to the previous release is unconditional.
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.