ci: update actions to v4 #1262
Merged
ci: update actions to v4 #1262
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
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.
Pull Request checklist
Note: these are not necessarily requirements
Pull Request description
Updated CI due to depreciation see https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Version 4 does not allow uploading Artifacts with the same name so I had to 'build-upload-merge-delete merged' for variants and debug builds. The warnings regarding 'release' builds should be gone also see marvinpinto/actions#695 (comment) as to why I changed the repo .. only thing I'm not sure about is whether or not we need to merge Artifacts within release builds also.. I can't test this on a fork so tagging @AKuHAK