Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nit] The PR description says "each pinned SHA is the commit the corresponding tag resolves to today." That's exact for
ruby/setup-ruby(@v1→a0102e0/ v1.324.0) andconfigure-rubygems-credentials(@v2.0.0→762a4b7), but not foractions/checkout:@v3currently resolves toa37ce91…(v3.6.0), whereas this pinsc85c95e…(v3.5.3). Pinning v3.5.3 is a deliberate, good choice — it matches the SHA the repo's ownSemgrep.ymlalready pins, and v3.5.3→v3.6.0 is immaterial togem build/gem push— so no code change is needed. Just consider tightening the wording (e.g. "SHAs are known-good tag versions; checkout is pinned to the same v3.5.3 as Semgrep.yml") so a future reader isn't surprised it isn't the current@v3tip. Non-blocking.