upgrade all gha packages to their latest node16 versions#156
Merged
ChrisLovering merged 4 commits intoNov 5, 2022
Merged
Conversation
onerandomusername
requested review from
Den4200,
MarkKoz and
jb3
as code owners
onerandomusername
force-pushed
the
update-actions-checkout
branch
from
d42eaa8 to
eba537a
Compare
Contributor
Author
|
I've changed this to upgrade every gha package that has an update which should solve most if not all of the deprecation warnings |
onerandomusername
changed the title
…o azure/k8s-deploy
ChrisLovering
approved these changes
Nov 5, 2022
Contributor
Author
|
I missed an actions/checkout@v2 in test.yaml. Not a big deal, as azure/setup-kubectl will need a bump at some point once they release a new version that doesn't use the set-ouput command |
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
3 participants
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.
got another one here 😄
I've checked the changelogs and upgraded this on my own projects, this seems to have the single change of changing from node 12 to node 16 which solves another bunch of warnings.