Repository navigation
Attach the jars to GitHub releases instead of CI runs - #5
Merged
Merged
Conversation
- release.yml: publishing a release builds its tag and uploads builds/*.jar to it (refuses a tag that doesn't match the project version). - build.yml: PR and main runs only build and verify; no jar artifacts. - README: point to the releases for downloads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
release.yml: publishing a GitHub release builds its tag and uploadsbuilds/*.jarto that release. It refuses a tag that does not match the project version (v0.6.0with 0.5.0 jars).build.yml: PR andmainruns only build and verify; they no longer upload jar artifacts.Test plan
v0.5.0and rejectsv0.6.0locally.build) green.v0.5.0attaches the 4 jars to the release.🤖 Generated with Claude Code