chore: force next release to 1.29.0 (Release-As)#263
Closed
VascoSch92 wants to merge 1 commit into
Closed
Conversation
Release-As: 1.29.0
Contributor
Endpoint audit❌ 6 off-contract call(s) — not on the agent-server · classifiers: cloud
❌ Not on agent-server (gated, 6)⛔ (no known backend) — served by no backend we can see (5)
|
Member
|
Happy to give it a stamp when you say you need, @VascoSch92 From PR description:
will work? |
Member
|
Closing as superseded by the 1.32.0 release path. PR #264 now updates the tracked agent-server image to v1.32.0 and includes merge instructions to preserve This comment was created by an AI agent (OpenHands) on behalf of Graham Neubig. |
auto-merge was automatically disabled
July 7, 2026 06:47
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The open release PR (#236) bumps to 2.0.0 because commit
f4222151—feat!: remove unused CloudProxyClient(#250) — carries a!breaking-change marker. That change was not actually consumer-breaking, so a major bump isn't warranted. Without it, the accumulatedfeat:commits are a minor bump → 1.29.0.This empty commit carries a
Release-As: 1.29.0footer to override Release Please's computed version. Once merged tomain, Release Please will rewrite PR #236 from2.0.0to1.29.0.This repo squash-merges with a blank commit body by default, which would strip the footer. Merge with the body set explicitly so
Release-As: 1.29.0lands onmain:(Release-As: 1.29.0)