Repository navigation
Fix CI publishing with a verified Maven toolchain - #46
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.
Summary
Why
Snapshot run 44272921635 failed for two distinct reasons: attempt 1 reached Central but received HTTP 502 during transfer; attempt 2 stopped before Maven ran because its ubuntu-latest ARM64 runner had no mvn executable (exit 127). This PR fixes the missing-toolchain failure only; it does not claim to resolve the earlier Central HTTP 502.
Validation
Release safety / next step
This PR does not dispatch a release, upload artifacts to Maven Central, change release versions, or create a stable tag. After merge and successful CI, snapshot verification requires a new release.yml dispatch at the merged main SHA; rerunning the old failed run would keep using its original workflow checkout. Any new snapshot upload and stable publication remain separately confirmed actions.
Note
Add pinned, SHA-512-verified Maven bootstrap to CI publishing workflows
shasumfallback), and refuses to extract on mismatch. It appends Maven's bin directory toGITHUB_PATH.scripts/test_*.pyfile, which now includes the new installer test suite in test_setup_maven.py.MavenSetupChecks.test_installs_without_using_system_mavenplaces a failingmvnstub on PATH; any CI job that still relies on a system Maven rather than the bootstrap will break.Macroscope summarized f737887.