Repository navigation
Conversation
The v0.2.0 release failed at the container step: Error: Failed to validate Maven distribution SHA-256, your Maven distribution might be compromised. process "chmod +x mvnw && ./mvnw -B -q -DskipTests dependency:go-offline" exit code 1 The pin is correct — the same URL hashes to 9c1ef917... locally, and the wrapper downloads and verifies it with a clean $HOME. What differs is the image: the wrapper shells out to curl/wget/unzip, which eclipse-temurin does not fully ship, so it produced a file that failed the checksum. The build stage now installs those tools and fetches Maven with an explicit sha256sum -c against the pin in .mvn/wrapper/maven-wrapper.properties. That keeps one source of truth, removes the wrapper's shell logic from the image, and fails with a usable message if the pin is ever wrong. Verified the exact RUN body locally: download, checksum OK, unpack, mvn -v reports 3.10.1 from /opt/apache-maven-3.10.1.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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.
The v0.2.0 release failed at the container step:
Error: Failed to validate Maven distribution SHA-256, your Maven distribution
might be compromised.
process "chmod +x mvnw && ./mvnw -B -q -DskipTests dependency:go-offline" exit code 1
The pin is correct — the same URL hashes to 9c1ef917... locally, and the wrapper downloads and verifies it with a clean $HOME. What differs is the image: the wrapper shells out to curl/wget/unzip, which eclipse-temurin does not fully ship, so it produced a file that failed the checksum.
The build stage now installs those tools and fetches Maven with an explicit sha256sum -c against the pin in .mvn/wrapper/maven-wrapper.properties. That keeps one source of truth, removes the wrapper's shell logic from the image, and fails with a usable message if the pin is ever wrong.
Verified the exact RUN body locally: download, checksum OK, unpack, mvn -v reports 3.10.1 from /opt/apache-maven-3.10.1.
What does this change?
Checklist
./mvnw verifypasses locallypython3 tools/smoke_test.pypasses againsttools/mock-upstream.pydocs/updated if an endpoint, config key or field changed.envfiles ordata/contents included