ci(release-please): authenticate via RELEASE_PLEASE_TOKEN PAT#14
Merged
Conversation
The default GITHUB_TOKEN triggers GitHub's anti-recursion safeguard: any workflow action taken with that token does NOT fire downstream workflows. For release-please that means: - Release PR opened → pull_request event doesn't fire → ci.yml never runs → branch protection blocks the merge. - Release-please tag created on PR merge → push-tag event doesn't fire → release.yml (goreleaser) never runs → binaries + .deb + .rpm + Homebrew formula never publish automatically. Both bit us during the v0.1.0 ship. Fix: authenticate the action with a dedicated fine-grained PAT (RELEASE_PLEASE_TOKEN). PAT-triggered events count as real user actions, so every downstream workflow fires normally. .github/SETTINGS.md updated to document the new secret and its required scopes (Contents R/W, Pull requests R/W, Workflows R/W, scoped to this repo only, ≤ 1-year expiration). After merge: release-please's next run uses the PAT, re-syncs the existing 0.1.1 release PR (the refreshing commit comes via PAT so CI fires correctly), and on merge the v0.1.1 tag push auto-fires goreleaser — no more manual close-reopen + workflow_dispatch dance.
amiwrpremium
added a commit
that referenced
this pull request
Apr 21, 2026
🤖 I have created a release *beep* *boop* --- ## [0.1.1](v0.1.0...v0.1.1) (2026-04-21) ### Bug fixes * **ci:** commit-msg regex accepts multiple parenthesised scopes ([#10](#10)) ([fa8a3ff](fa8a3ff)) * **codeql:** check Close() on writable file handles ([#13](#13)) ([43c0b80](43c0b80)) ### CI * **release-please:** authenticate via RELEASE_PLEASE_TOKEN PAT ([#14](#14)) ([7434055](7434055)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: AMiWR <83715695+amiwrpremium@users.noreply.github.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.
Swaps release-please action from default GITHUB_TOKEN to a fine-grained PAT so the tag-push + PR-creation events fire downstream workflows (ci.yml, release.yml) automatically. Fixes the manual close-reopen + workflow-dispatch dance we did for v0.1.0.
Requires the
RELEASE_PLEASE_TOKENrepo secret to exist before merge.