Repository navigation
ci: restrict CLA workflow token permissions and pin cla-check - #727
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Ahead of GitHub blocking
pull_request_targetby default on public repos (enforced 2026-12-02), this hardens the CLA workflow, which needs that trigger. The workflow is now explicitly allowed through anauthzedorg Actions event policy.permissions:block. The repo default token iswrite, whichpull_request_targetwould grant on every fork PR.authzed/actions/cla-checkto a commit SHA instead of@main. Thecla-checkcode is unchanged.This matches
authzed/spicedb'scla.yaml.See https://docs.github.com/en/actions/reference/security/securely-using-pull_request_target