ci: pin bazel-contrib/publish-to-bcr to full commit SHA#1496
Open
XananasX7 wants to merge 2 commits into
Open
Conversation
publish-to-bcr: @v2 -> @c316f1611511a40423572303f66c80bb30bfe2f8 (no v2 tag exists; pinned to HEAD of main at time of this patch)
eustas
approved these changes
Jul 3, 2026
eustas
left a comment
eustas
left a comment
Collaborator
There was a problem hiding this comment.
Please update to 005a51c75c5027e54477d290a21aa57e0a1a65f5
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
2 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.
publish_to_bcr.yamlreferencesbazel-contrib/publish-to-bcr@v2, but nov2tag exists in that repo — the reference currently resolves to HEAD ofmain. Pin to the explicit commit SHA to make the resolution deterministic and supply-chain safe:@v2→@c316f1611511a40423572303f66c80bb30bfe2f8Qualifies under the Google Open Source Patch Rewards Program.