Add warning about node16 deprecation #2887
Merged
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
JoannaaKL
reviewed
Sep 26, 2023
JoannaaKL
reviewed
Sep 26, 2023
JoannaaKL
approved these changes
Sep 26, 2023
|
cross-posting the issue I created below for visibility: The transition from Node 16 to Node 20 conflicts with the |
This was referenced Oct 10, 2023
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.
Add warning about node16 deprecation. This warning will be enabled on October 23rd, according to https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Right now it will be under FF
DistributedTask.AddWarningToNode16Action