Update github workflows to avoid deprecations #11475
Merged
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.
Description
Updating versions to avoid warnings and deprecations
Also modified deploy workflow to block using concurrency rather than lock script. That way only the
deploy
from the same branch can stop it, and it uses native github actions logic rather than custom scripts. we are already using this in CARTS and QMR. More info from QMR PR and docs for concurrencyAlso fixes application endpoint output to show up in summary
Note: these have already been tested in another PR and I'm migrating them here
DOCS:
aws-configure-credentials readme – no breaking changes between 1 and 4. ("By default, your account ID will not be masked in workflow logs. This was changed from being masked by default in the previous version. AWS does not consider account IDs as sensitive information, so this change reflects that stance." Let me know if you want to mask this still and I'll add that option)
cache readme – no breaking changes with v3
codeclimate action changelog – breaking changes not relevant to us
node version action – update allows us to read from .nvmrc natively
pre-commit/action changelog – doesn't specifically call out a fix but the warnings were resolved by upgrading
actions/checkout changelog – v3 uses node 16 which will be deprecated soon but doesn't have a warning for now, and keeps it up to date with our other checkouts@v3
dependabot/fetch-metadata action changelog – specifically by changing to @v1 it will automatically use latest version
Related ticket(s)
MDCT-none
How to test
All steps here pass
View the step summaries and notice no deprecation warnings (compare to main or other branches)