ci: update several eol actions #4194
Merged
Conversation
This file contains 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
Changes made: * docker/login-action v2 -> v3 * docker/metadata-action v4 -> v5 * docker/build-push-action v3 -> v5 * get-gke-credentials v1 -> v2 * helmfile v1 -> v2 * migrate actions-rs/toolchain -> dtolnay/rust-toolchain * remove docker/setup-qemu-action * remove battila7/get-version-action * removes unused container builds All of these were showing warnings. These upgrades *should* have zero side-effects for our CI, but I'll check post-merge and confirm that. Refs #3769, but does not close it: follow-up may be necessary post-merge, plus corresponding updates should be made across our repos.
conorsch
added
A-CI/CD
cratelyn
approved these changes
Apr 12, 2024
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.
Describe your changes
Changes made:
All of these were showing warnings. These upgrades should have zero side-effects for our CI, but I'll check post-merge and confirm that.
Issue ticket number and link
Refs #3769, but does not close it: follow-up may be necessary post-merge, plus corresponding updates should be made across our repos.
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: