Repository navigation
Pin Maven 3.9.16 for release publishing - #2125
Merged
Merged
Conversation
The ubuntu-latest runner now provides Maven 3.10. With it, central-publishing-maven-plugin 0.11.0 leaves maven-metadata-local.xml and _remote.repositories files in the Central bundle, because it only removes maven-metadata-central-staging.xml before bundling. Central rejected the v1.2.0-RC1 bundle with "Bundle has content that does NOT have a .pom file" for every module, and nothing was published. Download Maven 3.9.16 from Maven Central, verify its SHA-512, and put it on the PATH before publishing. This matches the version in .mise.toml. Maven 3.9 warns about the repositoryOrigins element in the shared settings file and still applies the central server credentials.
 |
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.2.0-RC1 release run (38299556979) failed at Central Portal validation:
The runner image changed between v1.1.8 (20260927, Maven 3.9) and RC1 (20261004, Maven 3.10). central-publishing-maven-plugin 0.11.0, the latest release, only deletes
maven-metadata-central-staging.xmlfrom its staging directory before bundling. Under Maven 3.10 the staging directory instead getsmaven-metadata-local.xmlat the artifact level and_remote.repositoriesfiles, and both end up in the bundle. Deployment 7eb04be3 failed validation and nothing reached Maven Central.I reproduced this locally by pointing the plugin at an unreachable
centralBaseUrl, so it stages and bundles but cannot upload. Maven 3.10.0 produced 18 extra bundle entries across three modules. Maven 3.9.16 produced none and logged thePre Bundling - deletedlines seen in the v1.1.8 run.This change downloads Maven 3.9.16 from Maven Central in the release workflow, verifies its SHA-512, and puts it on the PATH. The version matches
.mise.toml. Maven 3.9 warns about therepositoryOriginselement in.github/maven-settings.xmland still applies thecentralcredentials, so the shared settings file stays as it is for the snapshot workflow.Checked locally with actionlint 1.7.12 and a dry run of the new step.