Skip to content

Fix GitHub token usage in release workflow #287

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
DarthGigi merged 1 commit into from
Mar 12, 2026
Merged

Fix GitHub token usage in release workflow #287

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
6 changes: 4 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,8 @@ jobs:
id: stable_prep
run: node scripts/release-stable.mjs
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}
GH_TOKEN: ${{ secrets.PAT_TOKEN }}

- name: Create Stable GitHub Release
if: steps.stable_prep.outputs.release_ready == 'true'
Expand All @@ -104,4 +105,5 @@ jobs:
git push origin "$TAG"
gh release create "$TAG" --title "$TAG" --generate-notes --latest
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}
GH_TOKEN: ${{ secrets.PAT_TOKEN }}
5 changes: 3 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,9 +92,10 @@ Release behavior details:

- Changesets are authored in feature PRs and merged into `dev`.
- The release workflow commits version/changelog updates directly on the release branch (`dev` or `prod`) using `github-actions[bot]`.
- Stable release changes from `prod` are automatically synced back to `dev` by the release workflow to keep branches aligned.
- Stable release versioning is proposed via `changeset-release/prod` and merged into `prod` through a PR.
- Do **not** manually maintain `changeset-release/*` branches.
- Do **not** manually merge `prod` into `dev` for version sync; the workflow handles this.
- Avoid routine manual `prod` → `dev` sync merges unless you are intentionally bringing over a stable-only hotfix.
- The stable release workflow uses `PAT_TOKEN` for GitHub CLI release PR/release operations (required when repository setting **"Allow GitHub Actions to create and approve pull requests"** is disabled).

The version bump is determined automatically by changesets:

Expand Down
Loading