Repository navigation
Bump central-publishing-maven-plugin to 0.12.0 - #40
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
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.
Under Maven 3.10, which the GitHub Actions
ubuntu-latestimage now ships, plugin 0.8.0 leaves astray
maven-metadata-local.xmlat the artifact level of the staging directory, e.g.net/imglib2/imglib2/maven-metadata-local.xml. It ends up in the uploaded bundle, and Centralrejects the deployment:
This broke the imglib2 8.1.0 release:
https://github.com/imglib/imglib2/actions/runs/41253355902/job/124691280879
Reproduced locally by building the bundle without uploading. With 0.8.0, Maven 3.10.0 produces the
stray file and 3.9.14 / 3.9.16 don't. With 0.12.0 the bundle is clean on both 3.10.0 and 3.9.16.
🤖 Generated with Claude Code