Upgrade all third-party GitHub Actions and pin them to commit hashes#99
Open
Copilot wants to merge 4 commits into
Open
Upgrade all third-party GitHub Actions and pin them to commit hashes#99Copilot wants to merge 4 commits into
Copilot wants to merge 4 commits into
Conversation
…ases Agent-Logs-Url: https://github.com/ccao-data/ptaxsim/sessions/6a713e0a-e6b5-4788-b110-02df5c1a1351 Co-authored-by: jeancochrane <14170650+jeancochrane@users.noreply.github.com>
Open
10 tasks
jeancochrane
changed the title
jeancochrane
changed the title
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 PR upgrades all of our third-party GitHub Actions to ensure they are compatible with the upcoming Node 20 deprecation.
While we're at it, we also switch all of our references to third-party actions to point to commit hashes, so as to protect ourselves from the the ongoing scourge of supply chain attacks against third-party actions. These supply chain attacks work by pushing malicious code to running tags like
v2, which will then cause downstream workflows like ours to pull in the malicious code the next time they run.For all of our third-party actions, I sourced the commit hashes by checking the Releases page for the most recent release and copying the commit hash of that release. I also added inline comments indicating the version number that corresponds to the commit hash.
Test workflows to confirm these upgrades don't break anything:
pre-commit: https://github.com/ccao-data/ptaxsim/actions/runs/26308747272/job/77453411865R-CMD-check: https://github.com/ccao-data/ptaxsim/actions/runs/26308747264test-coverage: https://github.com/ccao-data/ptaxsim/actions/runs/26308747365pkgdown: https://github.com/ccao-data/ptaxsim/actions/runs/26308747360Connects https://github.com/ccao-data/aws-infrastructure/issues/59.