fix(ci): use GitHub App token in auto-release workflow - #1128
Conversation
The release-on-merge workflow was using secrets.GITHUB_TOKEN which lacks permission to dispatch other workflows. Switch to the same GitHub App token (RELEASE_APP_ID/RELEASE_APP_PRIVATE_KEY) used by release-bump-version.yml so gh workflow run succeeds.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review infoConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release workflow now uses a GitHub Apps token generated dynamically via Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
release-on-merge.ymlworkflow was failing withHTTP 403: Resource not accessible by integrationwhen trying to dispatchrelease-bump-version.ymlviagh workflow runsecrets.GITHUB_TOKENdoesn't have permission to trigger workflow dispatchesRELEASE_APP_ID/RELEASE_APP_PRIVATE_KEY) already used byrelease-bump-version.yml, which has the requiredactions: writescopeFixes: https://github.com/trycua/cua/actions/runs/22450965050/job/65018944677
Test plan
release:lumelabel and verify the auto-release workflow successfully dispatchesrelease-bump-version.ymlSummary by CodeRabbit