ci: pin PR title action to SHA and restrict permissions#13
Merged
Conversation
bdow
approved these changes
May 13, 2026
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Small hardening pass on our PR title workflow, based on a zizmor scan:
amannn/action-semantic-pull-requestto its commit SHA. Tags are mutable, so this protects us if the tag ever gets re-pointed.permissions: pull-requests: readso the job uses a minimal token instead of inheriting the default scopes.Functionally identical — the action just validates that PR titles follow conventional commits. Same fix as homebound-team/beam#1242.
Note: zizmor also flags
on: pull_request_targetas risky in general. Per the maintainer and GitHub Security Lab, it's safe here since we don't check out PR code — the two changes above are the recommended defense-in-depth on top.