Release Notes
Version history for the customer-managed parts of Agent Router. The management plane is operated by Tetrate and updated continuously, so it is not versioned here. This page tracks the components an operator installs and upgrades: the self-hosted data plane, the tare CLI, and the gateway. Entries are listed newest first.
What is tracked
| Component | Why it is versioned | Where it runs |
|---|---|---|
| Data plane | Installed and upgraded by the operator; the version determines available gateway behavior | Customer-managed Kubernetes |
tare CLI | Drives installation and upgrades; new subcommands and flags arrive here | Operator workstation or CI |
| Gateway | The Envoy-based proxy and its dynamic modules that enforce routing, guardrails, and cost | Inside the data plane |
The management plane, the Developer Console, and the Admin Dashboard are hosted by Tetrate and roll out continuously. Behavior changes that affect operators or developers are noted in the relevant release entry below.
How to read an entry
Each release is a second-level heading with its version and date. Changes are grouped under a fixed set of categories so a reader can scan for what matters:
- Added: new capabilities or endpoints.
- Changed: behavior that differs from the previous release.
- Fixed: resolved defects.
- Security: fixes and hardening with a security impact.
- Deprecated: capabilities scheduled for removal, with the target release.
- Upgrade notes: manual steps required to move from the previous version.
Upgrades are performed with tare upgrade. Any release that needs manual intervention says so in Upgrade notes; releases without that section upgrade in place with no additional steps.
Releases
This page is the template for tracking releases. Replace the illustrative entry below with real releases as they ship, keeping the newest at the top and reusing the category headings above.
0.0.0 — YYYY-MM-DD
The format for a release entry. Only the categories that apply to a release are included.
Added
- New capability, with a link to the guide or reference page that documents it.
Changed
- Behavior that differs from the previous release, stated so an operator can tell whether action is needed.
Fixed
- Defect that is now resolved.
Upgrade notes
- Any manual step required before or after running
tare upgrade. Omit this section when the upgrade is in place.
Related
- tare CLI reference: the commands used to install and upgrade the data plane
- Sizing and scale: capacity guidance to review before an upgrade
- Gateway behavior: the request-handling contract that release entries reference
Where to go next