ci: pin a-sync/s3-uploader to SHA (v2.0.1)#38
Open
mpinter wants to merge 1 commit into
Open
Conversation
Pin to commit 1b1020511c685aeb5be20f23190d2d1b63ab19a6. a-sync/s3-uploader was previously referenced via @master, which is a mutable ref controlled by the upstream maintainer. Any push to master would silently run in our backup workflow with AWS credentials. Pinning to an immutable SHA closes that supply-chain risk. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
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
1 participant
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.
Summary
a-sync/s3-uploader@master(mutable branch ref) with full-SHA pin@1b1020511c685aeb5be20f23190d2d1b63ab19a6(tagv2.0.1).Why
@masterfollows whatever the upstream maintainer pushes next. The action runs insidebackup-kubernetes-databases-inhouse.ymlwith AWS credentials available in env — a supply-chain push to upstream master would execute in our pipeline with those secrets. SHA pinning eliminates that class of risk.v2.0.1is the latest tagged release; the master branch currently points at the same commit, so this PR is functionally a no-op for current behavior.Test plan
backup-kubernetes-databases-inhouse.ymlresolves the action and uploads to S3 on the next scheduled run.🤖 Generated with Claude Code