Run Actions on Node 16 - #1000
Merged
henrymercer merged 7 commits intoMar 29, 2022
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
henrymercer
force-pushed
the
henrymercer/bump-node-js-to-v16
branch
from
f3c7153 to
9a709c1
Compare
March 28, 2022 15:39
cklin
reviewed
Mar 28, 2022
Comment thread
.github/update-release-branch.py
cklin
approved these changes
Mar 28, 2022
aeisenberg
reviewed
Mar 28, 2022
aeisenberg
left a comment
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
One small suggestion around the changelog.
Sorry, something went wrong.
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
Reviewers
3 participants
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.
This PR starts running the init, autobuild, analyze, and upload-sarif Actions on Node 16. This is a breaking change for customers using GitHub Connect or the Actions sync tool to pull in the latest version of the v1 Action on older GHES versions (GHES 3.1–3.3), therefore we are bumping to a new major version with this change.
We'll need to revert these changes in the v1 branch within the v2 -> v1 merge during the next release process.
Merge / deployment checklist