Bump all actions to latest and pin to release commit sha#3241
Open
jeremywiebe wants to merge 6 commits intomainfrom
Open
Bump all actions to latest and pin to release commit sha#3241jeremywiebe wants to merge 6 commits intomainfrom
jeremywiebe wants to merge 6 commits intomainfrom
Conversation
Contributor
🗄️ Schema Change: No Changes ✅ |
Contributor
npm Snapshot: NOT PublishedOh noes!! We couldn't find any changesets in this PR (348986a). As a result, we did not |
Contributor
|
Size Change: 0 B Total Size: 484 kB ℹ️ View Unchanged
|
Contributor
🛠️ Item Splitting: No Changes ✅ |
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:
This PR updates all of our Github Action workflows to use the latest version of each action we use. I've pinned each action to the commit sha of that version to ensure our actions don't "version drift" and so that we have control over when we upgrade in the future.
Issue: LEMS-3892
Test plan:
Run all actions. The only one that we can't test ahead of time is the release workflow, but if all other actions are fine, then there is a high likelihood that the release one will be fine also. And if it fails, we can fix and cut another release.