-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[actions] update to latest action using node20 instead of deprecated node16 #371
Conversation
for upload-artifacts@v4 see: |
should we even upgrade then? |
Nvm. It was already broken |
No, please don't upgrade those. This will break release creation. |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin next
git worktree add -d .worktree/backport-371-to-next origin/next
cd .worktree/backport-371-to-next
git switch --create backport-371-to-next
git cherry-pick -x cc3a5d19b8897d9a6e8c4f7307571c62a5bdcd36 |
Manually backported it to next |
Git push to origin failed for legacy with exitcode 1 |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin next
git worktree add -d .worktree/backport-371-to-next origin/next
cd .worktree/backport-371-to-next
git switch --create backport-371-to-next
git cherry-pick -x cc3a5d19b8897d9a6e8c4f7307571c62a5bdcd36 |
Currently each pipeline has warnings to it regarding the deprecation of node.js 16 actions like:
This PR updates the versions of the pipeline accordingly.
See also:
https://github.com/actions/checkout/releases
https://github.com/korthout/backport-action/releases
https://github.com/softprops/action-gh-release/releases