Repository navigation
fix: make release checksums verify beside jars - #13
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.
Release checksum files currently name
target/<jar>, sosha256sum -cfails when users download the JAR and checksum into the same directory. Generate the checksum from insidetarget/and check it before publishing; future release assets will verify side by side.Validation: parsed the workflow, ran its checksum step against the published JAR, then verified the JAR and resulting checksum in a separate flat download directory. The version gate reports
publish: Falsefor this workflow-only change. Existing release assets remain unchanged.