Fix Maven version derivation (v1.0.0 release collided at 0.50.0) - #343
Open
jgowdy wants to merge 1 commit into
Open
Fix Maven version derivation (v1.0.0 release collided at 0.50.0)#343jgowdy wants to merge 1 commit into
jgowdy wants to merge 1 commit into
Conversation
…it tag The Java artifact version was derived as 0.50.<git-tag-patch>. That collided once the repo moved off the v0.5.x tag line: the v1.0.0 release produced patch 0 -> 0.50.0, which already existed in GitHub Packages, failing the deploy with a 409 Conflict. Derive the next 0.50.x by reading the latest published version from the GitHub Packages maven-metadata.xml and incrementing - tag-independent, monotonic, and collision-free. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jgowdy
enabled auto-merge (squash)
June 20, 2026 03:20
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
1 participant
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.
The v1.0.0 release's Maven publish failed with a 409 Conflict: the workflow derived the Java version as
0.50.<git-tag-patch>, andv1.0.0→ patch0→0.50.0, which already exists in GitHub Packages (from the oldv0.5.0release).Fix: derive the next
0.50.xfrom the latest published version in the GitHub Packagesmaven-metadata.xmland increment — tag-independent and collision-free. (This release's Java artifact was already published manually as0.50.116via workflow_dispatch.)