Skip to content

fix(release): use organization token for release PR #171

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
Teakowa merged 1 commit into from
Aug 18, 2026
+8 −6
Merged

fix(release): use organization token for release PR #171

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
8 changes: 5 additions & 3 deletions .github/workflows/release-please.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,19 +29,21 @@ jobs:
with:
fetch-depth: 0
persist-credentials: true
token: ${{ github.token }}
token: ${{ secrets.GH_TOKEN }}

- name: Run release-please
id: release
uses: googleapis/release-please-action@v4
env:
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
with:
token: ${{ github.token }}
token: ${{ secrets.GH_TOKEN }}
config-file: release-please-config.json
manifest-file: .release-please-manifest.json

- name: Synchronize checked-in release metadata
env:
GH_TOKEN: ${{ github.token }}
GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
PR: ${{ steps.release.outputs.pr }}
run: |
set -euo pipefail
Expand Down
6 changes: 3 additions & 3 deletions docs/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,9 +137,9 @@ before attaching them to the draft Release.

### Repository configuration

Enable Actions to create and approve pull requests, and grant the default
repository `GITHUB_TOKEN` `contents: write`, `issues: write`, and
`pull-requests: write` for the release-please workflow. The reusable distribution workflow also needs
Enable Actions to create and approve pull requests. The release-please workflow
uses the repository's `GH_TOKEN` secret as `GITHUB_TOKEN` so it can create and
update the Release PR. The reusable distribution workflow also needs
`id-token: write` for npm provenance and `packages: write` for GitHub Packages.
Create a protected `release` environment if publication approval is required;
the final `publish-release` job is the only job that uses it.
Expand Down
Loading