ci: use RELEASE_PAT to bypass branch protection for semantic-release#148
ci: use RELEASE_PAT to bypass branch protection for semantic-release#148infloent wants to merge 1 commit into
Conversation
| # ENV and Config | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| GITHUB_TOKEN: ${{ secrets.RELEASE_PAT }} |
There was a problem hiding this comment.
- RELEASE_PAT created but access approval pending
|
New token can be from service account, then we can keep this as permanent solution. |
@easingthemes me and Hugo don't have access to create a token from a service account, that's why we open this issue #147 for the temp solution while there is #146 issue for the permanent solution. The goal for the temp solution is to unblock the release fast (without coordinating with multiple persons for access ) in order to:
|
Description
Temp fix: use
RELEASE_PATto unblock semantic-release onmainCloses #147, ref #146.
The default
GITHUB_TOKENcannot bypass branch protection, causing the release workflow to fail withGH006on every push tomain. This swaps inRELEASE_PAT(a fine-grained PAT scoped to this repo, Contents: Read and write) as a temporary fix while the org GitHub App is provisioned.Changes:
release.yml-GITHUB_TOKEN->RELEASE_PATmanual-release.yml-GITHUB_TOKEN->RELEASE_PATVerified via
manual-release.ymldry-run on this branch - noGH006error.This is temporary. Remove
RELEASE_PATand revert these changes once the GitHub App solution from #146 is in place.Related Issue
#147
Fixes #
Types of changes
Checklist: