Move action using node12 to a newer version #3722
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.
Node12 has been out of support since April 2022. As a result GH has started the deprecation process of Node12 for GitHub Actions by migrating all actions to run on Node16 (read
more). The
softprops/action-gh-release
action's version which we used in thebuild.yml
workflow was running on Node12. But a newer version (v0.1.15
) of the action is run on Node16. We're swithing to using that newer version. This should makeThe following actions uses node12 which is deprecated and will be forced to run on node16: softprops/action-gh-release@1e07f4...
annotation disappear from the details of the workflow runs.The upgrade may also remove the
The "set-output" command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
annotation.Latest build: extension-builds-3722 (as of Sat, 13 Apr 2024 18:02:51 GMT).