Skip to content

Pin GitHub Actions to full commit SHAs - #233

Open
goanpeca wants to merge 1 commit into
Backblaze:masterfrom
goanpeca:chore/pin-actions
Open

goanpeca wants to merge 1 commit into
Backblaze:masterfrom
goanpeca:chore/pin-actions

Conversation

@goanpeca

Copy link
Copy Markdown

Pins every GitHub Action in this repo's workflows to a full commit SHA with the exact release in a comment (owner/action@<sha> # vX.Y.Z), staying within the major version each workflow already used, so behaviour does not change. Tags and branches can be moved to different code after the fact; a commit SHA cannot. This is the step needed before the Backblaze org can turn on GitHub's "require actions to be pinned to a full-length commit SHA" policy, which backblaze-labs and backblaze-b2-samples already enforce.

Action Was Now
actions/checkout v4 v4.4.0
actions/setup-java v4 v4.9.1
astral-sh/setup-uv v5 v5.4.2
crazy-max/ghaction-github-pages v3 v3.2.0
crazy-max/ghaction-github-status v4 v4.2.0
gradle/actions v4 v4.4.4
softprops/action-gh-release v2 v2.6.2

Checked: actionlint reports no new findings.

Signed-off-by: Gonzalo Peña-Castellanos <goanpeca@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant