Pin backport actions to SHAs - #16996
Merged
Merged
Conversation
This can be required by repo configuration and is considered a GitHub Actions security best practice.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the shared backport workflow to follow GitHub Actions security guidance by pinning third-party actions to immutable commit SHAs, improving supply-chain integrity for repos that consume this workflow.
Changes:
- Pin
actions/github-scriptusages to a specific commit SHA (annotated asv9.0.0). - Pin
actions/checkoutusage to a specific commit SHA (annotated asv6.0.3).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ViktorHofer
approved these changes
Jun 10, 2026
Member
|
/backport to release/10.0 |
Contributor
|
Started backporting to |
Contributor
|
@JanProvaznik backporting to git am output$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Pin backport actions to SHAs
Using index info to reconstruct a base tree...
M .github/workflows/backport-base.yml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/backport-base.yml
CONFLICT (content): Merge conflict in .github/workflows/backport-base.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Pin backport actions to SHAs
Error: The process '/usr/bin/git' failed with exit code 128 |
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
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.
This can be required by repo configuration and is considered a GitHub Actions security best practice.
I turned the setting on in dotnet/msbuild and got errors like https://github.com/dotnet/msbuild/actions/runs/27234807068.
To double check: