chore(ci): migrate all workflows from PAT to GitHub App token [SEC-58]#287
chore(ci): migrate all workflows from PAT to GitHub App token [SEC-58]#287
Conversation
- Migrated draft-new-release.yml to use GitHub App token - Migrated publish-new-release.yml to use GitHub App token - Added explicit permissions at job level with comments - Fixed template-injection security issue in publish-new-release.yml - PRs created by these workflows will now trigger CI checks Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> 🔒 Scanned for secrets using gitleaks 8.30.0
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the
✨ 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 |
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> 🔒 Scanned for secrets using gitleaks 8.30.0
…-release.yml [SEC-58] 🔒 Scanned for secrets using gitleaks 8.30.0
- Use env.GH_TOKEN instead of with: token - Use branch-name instead of branch - Remove invalid params: force, tags, ref - Add files parameter - Use tag parameter for tag creation 🔒 Scanned for secrets using gitleaks 8.30.0
|



Summary
Files Changed
.github/workflows/draft-new-release.yml- Migrated to GitHub App Token + Signed Commits.github/workflows/publish-new-release.yml- Migrated to GitHub App Token + Signed Commits (updated with additional fix)Migration Details
- Moved permissions to job level
- Used App Token for checkout and all git operations
- Replaced
git pushwithryancyq/github-signed-commitaction- PR creation will now trigger CI
- Moved permissions to job level
- Fixed template-injection vulnerability by moving untrusted input to env var
- Used App Token for all operations
- Replaced
git push --deletewith GitHub API call and signed commit action- PR creation will now trigger CI
Latest Fix (January 29, 2026)
publish-new-release.yml additional improvements:
git push --delete origin $TAGwith GitHub API call (gh api DELETE /repos/.../git/refs/tags/...)Signed Commits Implementation
Both workflows now use
ryancyq/github-signed-commit@e9f3b28c80da7be66d24b8f501a5abe82a6b855f # v1.2.0to ensure all pushes are signed and verified:publish-new-release.yml:
git tag -a && git pushwith signed commit action for tag pushesgit push --deletewith GitHub API for tag deletiondraft-new-release.yml:
git push --set-upstream originwith signed commit action for branch creationgit push origin --tagsandgit push --follow-tagswith signed commit actionSecurity Improvements
Test plan
🤖 Generated with Claude Code