Repository navigation
Add release workflow (tag → GitHub Release with jar) - #6
Merged
Merged
Conversation
Runs on a v* tag push, or manually with tag / target / java-version inputs so older commits (e.g. 1.0.0, which needs JDK 21) can be released too; the tag is created at target if it doesn't exist. Builds with ./mvnw when present (falls back to mvn), attaches the jar, and uses the matching CHANGELOG.md section from main as release notes. Workflow inputs reach shell steps only through env vars. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018syaxkhsW9ioZChSmth9Xx
MrPippi
marked this pull request as ready for review
October 9, 2026 02:20
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
2 participants
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
Adds
.github/workflows/release.yml, which builds the plugin for a tag and publishes it as a GitHub Release with the jar attached.Why: we want
v1.0.0released at6c3257cfor Paper 1.21.x users. The session that prepared this can only push to its working branch, so it cannot push tags (HTTP 403), and its GitHub tools have no way to create a release. Doing it withGITHUB_TOKENinside Actions works, and the same workflow can publish v2.0.0 and later versions.How it runs
v*: releases that tag, built on JDK 25.tag: requiredtarget: the commit to tag, needed only if the tag doesn't exist yetjava-version: defaults to25; 1.x needs21./mvnw -B verify, or plainmvnfor commits that predate the wrapper (such as6c3257c), so tests must pass before anything is published.## [x.y.z]section ofCHANGELOG.mdonmain. If there is no matching section, a one-line placeholder is used.gh release create --target <sha>creates the tag on the server. Tags created byGITHUB_TOKENdo not re-trigger the workflow, so there is no double run.env, never by interpolating them into scripts. Permissions arecontents: writeonly.After merge
Run it with
tag=v1.0.0,target=6c3257c1…,java-version=21.Test plan
AutoPickup-1.0.0.jar🤖 Generated with Claude Code
https://claude.ai/code/session_018syaxkhsW9ioZChSmth9Xx
Generated by Claude Code