-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[node] update node@16 deprecation day #11671
Merged
kodiakhq
merged 5 commits into
main
from
trek/zero-2076-update-node-16-deprecation-message-to-reference-new-end-of
May 30, 2024
Merged
[node] update node@16 deprecation day #11671
kodiakhq
merged 5 commits into
main
from
trek/zero-2076-update-node-16-deprecation-message-to-reference-new-end-of
May 30, 2024
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
🦋 Changeset detectedLatest commit: f44d74c The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
trek
requested review from
TooTallNate,
EndangeredMassa,
onsclom,
jeffsee55 and
erikareads
as code owners
May 29, 2024 20:34
TooTallNate
previously approved these changes
May 29, 2024
…ference-new-end-of' of github.com:vercel/vercel into trek/zero-2076-update-node-16-deprecation-message-to-reference-new-end-of
TooTallNate
previously approved these changes
May 29, 2024
onsclom
previously approved these changes
May 29, 2024
EndangeredMassa
approved these changes
May 30, 2024
kodiakhq
bot
deleted the
trek/zero-2076-update-node-16-deprecation-message-to-reference-new-end-of
branch
May 30, 2024 15:24
Merged
trek
pushed a commit
that referenced
this pull request
May 30, 2024
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @vercel/python@4.3.0 ### Minor Changes - support newer python versions ([#11675](#11675)) ## @vercel/build-utils@8.2.1 ### Patch Changes - [node] update node@16 deprecation day ([#11671](#11671)) ## vercel@34.2.4 ### Patch Changes - Updated dependencies \[[`3eb9d8c89`](3eb9d8c), [`83741a0eb`](83741a0)]: - @vercel/python@4.3.0 - @vercel/build-utils@8.2.1 - @vercel/node@3.1.6 - @vercel/static-build@2.5.10 ## @vercel/client@13.2.8 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0)]: - @vercel/build-utils@8.2.1 ## @vercel/gatsby-plugin-vercel-builder@2.0.32 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0)]: - @vercel/build-utils@8.2.1 ## @vercel/node@3.1.6 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0)]: - @vercel/build-utils@8.2.1 ## @vercel/static-build@2.5.10 ### Patch Changes - Updated dependencies \[]: - @vercel/gatsby-plugin-vercel-builder@2.0.32 ## @vercel-internals/types@1.0.37 ### Patch Changes - Updated dependencies \[[`83741a0eb`](83741a0)]: - @vercel/build-utils@8.2.1 Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
trek
added a commit
that referenced
this pull request
Jun 6, 2024
#11671 changed the EOL date for node 16.x to be AWS's final date. We want ours to be ~ a month earlier.
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.
Double check my dates, but I believe this is the new correct date we want. https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html