ci: change to v4 actions / upgrade to NodeJS 20#100
Merged
Conversation
skwasjer
force-pushed
the
chore/change_to_v4_deprecate_nodejs_20
branch
from
1858340 to
6204086
Compare
|
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.
Due to NodeJS 16 being EOL, GH actions must be upgraded.
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/
The only action for which there is no update to NodeJS 20 yet is:gittools/actions/gitversion.GitTools/actions#1021
With this upgrade, we also get improved upload/download artifact actions performance, removing the need for our custom tar actions. See actions/upload-artifact#199