Skip to content

ci: use the PAT secret for release-please #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fty4 merged 1 commit into from
Nov 1, 2026
Merged

ci: use the PAT secret for release-please #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/release-please.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,9 @@ jobs:
- id: release
uses: googleapis/release-please-action@v4
with:
# A token from a user (secret RELEASE_PLEASE_TOKEN) makes the release PR
# A token from a user (secret PAT) makes the release PR
# trigger the normal checks; the default GITHUB_TOKEN does not.
token: ${{ secrets.RELEASE_PLEASE_TOKEN || secrets.GITHUB_TOKEN }}
token: ${{ secrets.PAT || secrets.GITHUB_TOKEN }}
config-file: release-please-config.json
manifest-file: .release-please-manifest.json

Expand Down
4 changes: 2 additions & 2 deletions docs/releasing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,12 +29,12 @@ with the default `GITHUB_TOKEN` does not trigger other workflows, so a separate

A release PR created with the default `GITHUB_TOKEN` does not run the `test`
workflow, so required checks on `main` could never pass. The workflow therefore
uses the repository secret `RELEASE_PLEASE_TOKEN` when it exists and falls back
uses the repository secret `PAT` when it exists and falls back
to `GITHUB_TOKEN` otherwise. Create a fine-grained personal access token (of a
user who may push to the repository) with access to this repository only and
the permissions **Contents: read and write**, **Pull requests: read and write**
and **Issues: read and write**, give it an expiry, and store it as the secret
`RELEASE_PLEASE_TOKEN` (Settings > Secrets and variables > Actions). Put the
`PAT` (Settings > Secrets and variables > Actions). Put the
expiry date in your calendar: when the token expires the release PR silently
stops getting its checks.

Expand Down
Loading