Skip to content

ci(release): push CHANGELOG to develop via RELEASE_TOKEN PAT #12

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

ci(release): push CHANGELOG to develop via RELEASE_TOKEN PAT #12

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: 6 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,12 @@ jobs:
fetch-depth: 0
# Check out the branch (not the detached tag) so we can commit CHANGELOG.md back.
ref: develop
# Push back to develop with a PAT, not the default GITHUB_TOKEN: the
# `protect-develop` ruleset blocks direct pushes, and the GitHub Actions
# bot cannot be a bypass actor on a user-owned repo. A PAT owned by an
# admin is attributed to that admin, whom the ruleset's admin bypass
# already covers. RELEASE_TOKEN: fine-grained PAT, Contents: read/write.
token: ${{ secrets.RELEASE_TOKEN }}

- uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
with:
Expand Down
Loading