Skip to content

chore(agentgateway): run 2.5.0, the stable of 2.5.0-rc.4 - #488

Merged
teemow merged 3 commits into
giantswarmfrom
fork/agentgateway-2.5.0-stable
Oct 19, 2026
Merged

teemow merged 3 commits into
giantswarmfrom
fork/agentgateway-2.5.0-stable

Conversation

@teemow

@teemow teemow commented Oct 19, 2026

Copy link
Copy Markdown
Member

Problem

The 1.16.0 candidates run agentgateway 2.5.0-rc.2, a release candidate. Every stable Substrate before them ran a stable agentgateway, so 1.16.0 would be the first stable on a candidate dataplane.

Proposed solution

Pin agentgateway 2.5.0, the stable of v2.5.0-rc.4 (913dbe92): 2.5.0-rc.2 plus

The pin moves together in .circleci/config.yml, charts/substrate/values.yaml and the e2e's agentgateway component, by digest sha256:e48f9d4f…. hack/verify/agentgateway-image.sh passes. FORK.md and the 1.15 → 1.16 upgrade notes now name 2.5.0.

Acceptance criteria

  • run-tests and govulncheck green
  • The resulting v1.16.0 candidate passes agentlab's substrate-step-test from the released platform's Substrate: the conversation resumes, the durable volume is intact, and a new conversation starts on the golden. The candidate is promoted to 1.16.0 only after that.

Before this pin, v1.16.0-rc.3 (on 2.5.0-rc.2) passed the same step check from 1.13.1, all 8 stages.

agentgateway 2.5.0 is the stable of 2.5.0-rc.4 on the same commit: the
2.5.0-rc.2 the line ran, plus every address of the gateway counted local
for a tcp rule and a policy denial answered 403 naming the destination
and where it is allowed. A stable Substrate runs a stable agentgateway.
@teemow
teemow requested a review from a team as a code owner October 19, 2026 18:44
@teemow
teemow merged commit 865b1b3 into giantswarm Oct 19, 2026
20 checks passed
@teemow
teemow deleted the fork/agentgateway-2.5.0-stable branch October 19, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant