Repository navigation
Remove the Maven 3.9 pin from the release workflow - #874
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.
Fixes #870
Checklist
Description
The publish job downloaded Maven 3.9.16 because under the runner's Maven 3.10, central-publishing-maven-plugin 0.11.0 put
maven-metadata-local.xmland_remote.repositoriesin the bundle and Central rejected it. 0.12.0 (#848) fixes that, and 14.3.0 published fine with it (still under the pin). So the "Setup Maven 3.9" step goes and the job uses the runner's Maven again.Locally a Maven 3.10.0 + 0.12.0 bundle has neither file. actionlint passes. Whether Central accepts a bundle built under 3.10 only shows on the next release.
🤖 Generated with Claude Code