ci: pin GitHub Actions to commit SHAs (12)#474
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
WalkthroughSeven GitHub Actions workflows replace version-tagged action references with pinned commit SHAs. Existing triggers, commands, inputs, publishing, release, and Pages deployment behavior remain unchanged. ChangesWorkflow action pinning
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Why
Mutable Action tags (
@v4,@main) can be retagged, which is a supply-chain risk.This PR pins third-party Actions to full commit SHAs while keeping the tag in a comment.
Official
actions/*tags are left unchanged (common maintainer preference).Pins
pnpm/action-setup@v3 -> a3252b78c470actions/configure-pages@v2 -> c5a3e1159e0cactions/jekyll-build-pages@v1 -> 44a6e6beabd4actions/upload-pages-artifact@v3 -> 56afc609e742actions/deploy-pages@v4 -> d6db90164ac5pnpm/action-setup@v4 -> b906affcce14pnpm/action-setup@v2 -> eae0cfeb286esoftprops/action-gh-release@v1 -> de2c0eb89ae2pnpm/action-setup@v4 -> b906affcce14pnpm/action-setup@v4 -> b906affcce14pnpm/action-setup@v4 -> b906affcce14pnpm/action-setup@v4 -> b906affcce14Reference: GitHub docs on using third-party actions securely.
Summary by CodeRabbit