Repository navigation
UID2-8138: set VERSION_NAME to 2.2.0-SNAPSHOT after the 2.1.1 release - #154
Closed
cYKatherine wants to merge 1 commit into
Closed
cYKatherine wants to merge 1 commit into
cYKatherine wants to merge 1 commit into
Conversation
The 2.1.1 release left main on the release version because the next-snapshot commit was empty. A push to main then tries to publish 2.1.1 again instead of a snapshot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Closing: we're not publishing anything from this repo for now. Note for whoever does the next release: |
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.
mainhas been onVERSION_NAME=2.1.1since the 2.1.1 release on 2026-10-05. The release's "Prepare next development version: 2.2.0-SNAPSHOT" commit (4118b2d) came out empty, which is the bug #153 fixed, so the snapshot bump never landed.With a release version on
main, the next push runs the "Deploy SNAPSHOT" step inbuild.ymlwith2.1.1, which tries to republish an already-released version instead of a snapshot. This sets it to the intended2.2.0-SNAPSHOT.Merging this also gives the first real use of the rotated
GPG_KEY/GPG_PASSPHRASE(this repo now signs with the same key as the Java SDKs, UID2-8138); I'll verify the snapshot's signature after it publishes.🤖 Generated with Claude Code