Repository navigation
Pin Maven 3.9.16 for clean Central release bundles - #48
Merged
Merged
Conversation
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.
Maven Central rejects the 5.8.0 release because Maven 3.10 adds
org/openpatch/scratch/maven-metadata-local.xmlto the publishing bundle. The release runner recently changed from Maven 3.9.16 to 3.10.0, and updating the Central publishing plugin alone did not remove the extra entry.Pin both release jobs to Maven 3.9.16 using a shared setup action with a fixed SHA-512 checksum. Print the Maven version before publication so the toolchain is visible in release logs.
Validation: reproduced the extra bundle entry with Maven 3.10.0 and confirmed it is absent with 3.9.16, using a local unreachable publishing endpoint. Executed the setup action's download, checksum verification, and version check locally.