Fix release CI: executable gradlew on tag builds + dev_build contents:write - #8
Merged
Merged
Conversation
…ld contents:write release.yml builds the checked-out tag, but tags up to v1.3.5 were committed with gradlew at mode 100644 (no exec bit), so `./gradlew` failed with "Permission denied" (exit 126). chmod it before invoking. dev_build.yml's snapshot Release step needs contents:write; the repo's default token is read-only, so the publish step was 403-ing on every push to main. Co-Authored-By: Claude Opus 4.8 <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
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.
Why the release wasn't building
The
Publish Releaseworkflow (release.yml) checks out the named version tag and builds it. Every release tag up to v1.3.5 was committed withgradlewat mode100644(no exec bit), so the runner hit:The exec bit was fixed on
main's HEAD (100755), but existing tags are frozen at100644, so dispatching a release for v1.3.5 still failed.Separately,
dev_build.yml's snapshotReleasestep was 403-ing onmainbecause the defaultGITHUB_TOKENis read-only (contents: read).Fixes
chmod +x ./gradlewbefore invoking it, so tag builds work regardless of the tag's frozen file mode.permissions: contents: writeso the snapshot publish step can create/update the Dev Build release.After merge, the official v1.3.5 release jar will be (re)built and attached via
release.ymlworkflow_dispatch.🤖 Generated with Claude Code