[PR #470] [MERGED] fix(release): let release PR updates trigger CI #2016

New issue

Closed

opened 2026-10-16 21:13:24 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:13:24 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/470
Author: @morluto
Created: 8/9/2026
Status: ✅ Merged
Merged: 8/9/2026
Merged by: @morluto

Base: main ← Head: fix/release-please-ci-auth

📝 Commits (1)

75ec0cc fix(release): let release PR updates trigger CI

📊 Changes

1 file changed (+5 additions, -2 deletions)

View changed files

📝 .github/workflows/release.yml (+5 -2)

📄 Description

Description

Release-please currently mutates its pull request with the workflow GITHUB_TOKEN. GitHub deliberately places pull_request workflows caused by that token into action_required, so every release-PR update needs a manual workflow approval before required checks can run.

Use a dedicated RELEASE_PLEASE_TOKEN for both mutations of the release branch: the release-please action and the follow-up canonical catalog commit. Keeping the same identity for both pushes is essential; otherwise the catalog normalization commit reintroduces the approval gate. The existing GITHUB_TOKEN remains a transition fallback, preserving today’s manual-approval behavior until the dedicated credential is provisioned.

The intended credential is a narrowly scoped GitHub App installation token, or a fine-grained PAT with repository contents and pull-request write access. The locally configured broad classic PAT was intentionally not copied into Actions.

Type of Change

Bug fix

Testing Performed

TypeScript typecheck passes (npm run typecheck)
Linting passes (npm run lint)
npm run format:check -- .github/workflows/release.yml — passed
git diff --check — passed

Tool Contract Impact

None.

Observed on release PR #463.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/470 **Author:** [@morluto](https://github.com/morluto) **Created:** 8/9/2026 **Status:** ✅ Merged **Merged:** 8/9/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/release-please-ci-auth` --- ### 📝 Commits (1) - [`75ec0cc`](https://github.com/morluto/rea/commit/75ec0cc992c3404e0f6c38b9656dc7e4ad0c73a3) fix(release): let release PR updates trigger CI ### 📊 Changes **1 file changed** (+5 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+5 -2) </details> ### 📄 Description ## Description Release-please currently mutates its pull request with the workflow `GITHUB_TOKEN`. GitHub deliberately places `pull_request` workflows caused by that token into `action_required`, so every release-PR update needs a manual workflow approval before required checks can run. Use a dedicated `RELEASE_PLEASE_TOKEN` for both mutations of the release branch: the release-please action and the follow-up canonical catalog commit. Keeping the same identity for both pushes is essential; otherwise the catalog normalization commit reintroduces the approval gate. The existing `GITHUB_TOKEN` remains a transition fallback, preserving today’s manual-approval behavior until the dedicated credential is provisioned. The intended credential is a narrowly scoped GitHub App installation token, or a fine-grained PAT with repository contents and pull-request write access. The locally configured broad classic PAT was intentionally not copied into Actions. ## Type of Change - [x] Bug fix ## Testing Performed - [x] TypeScript typecheck passes (`npm run typecheck`) - [x] Linting passes (`npm run lint`) - [x] `npm run format:check -- .github/workflows/release.yml` — passed - [x] `git diff --check` — passed ## Tool Contract Impact None. ## Related Issues Observed on release PR #463. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-16 21:13:24 +00:00

closed this issue
added the
pull-request
label

Rows
Columns