Repository navigation
ci: publish latest jar to a stable release - #7
Merged
Merged
Conversation
Adds a publish job, gated to push-on-main, that uploads the built jar to a fixed `latest`-tagged release so it can be downloaded from a stable URL instead of hunting a run SHA. Kept as a separate job with its own contents:write permission and concurrency group so the build job stays read-only and a rapid double-push can't cancel an in-flight upload. Co-Authored-By: Claude Sonnet 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
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.
Adds a
publishjob that runs only on push tomainand uploads thebuilt jar to a fixed
latest-tagged GitHub Release, so the newestjar is always at a stable URL instead of a per-commit artifact SHA.
buildjob stayspermissions: contents: read, unchanged behavior.publishjob (needs: build) gets its owncontents: write,downloads the jar the build job already produced instead of
rebuilding, and runs only when
github.event_name == 'push' && github.ref == 'refs/heads/main'.cancel-in-progress, so a rapiddouble-push can't cancel an in-flight release upload mid-write.
&&/||chain, so a real upload failure isn't masked by amisleading "release already exists" error.
Reviewed by code-reviewer (APPROVE) and security-specialist (PASS),
both 0 CRITICAL/HIGH; the MEDIUM findings from both are addressed
above.