Pin codecov/codecov-action to v7.0.0 SHA (GHO-261)#390
Open
sayo-ep wants to merge 1 commit into
Open
Conversation
Justin Hammond (Justintime50)
approved these changes
Jul 20, 2026
sayo-ep
force-pushed
the
sayo/gho-261-pin-codecov-v7
branch
from
July 20, 2026 17:48
71e4d0a to
c3aa356
Compare
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.
Pins
codecov/codecov-actionfrom the floating@v5tag to v7.0.0 at commitfb8b3582c8e4def4969c97caa2f19720cb33a72f, per the security review in GHO-261.The v5 line never received the VULN-1652 template-injection hardening (fixed upstream in v6.0.1); v7.0.0 is the reviewed remediation target, and pinning to a full commit SHA removes the mutable-tag risk. Canary verified green in EasyPost/shentry#23.
Ref: GHO-261