Skip to content
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

Conversation

trek
Copy link
Contributor

@trek trek commented May 29, 2024

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

Copy link

changeset-bot bot commented May 29, 2024

🦋 Changeset detected

Latest commit: f44d74c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages
Name Type
@vercel/build-utils Patch
vercel Patch
@vercel/client Patch
@vercel/gatsby-plugin-vercel-builder Patch
@vercel/node Patch
@vercel/static-build Patch
@vercel-internals/types Patch

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 trek marked this pull request as ready for review May 29, 2024 20:34
TooTallNate
TooTallNate previously approved these changes May 29, 2024
trek added 2 commits May 29, 2024 15:50
…ference-new-end-of' of github.com:vercel/vercel into trek/zero-2076-update-node-16-deprecation-message-to-reference-new-end-of
TooTallNate
TooTallNate previously approved these changes May 29, 2024
onsclom
onsclom previously approved these changes May 29, 2024
@trek trek dismissed stale reviews from onsclom and TooTallNate via f44d74c May 29, 2024 23:45
@trek trek added the pr: automerge Automatically merge the PR when checks pass label May 30, 2024
@trek trek requested review from TooTallNate and onsclom May 30, 2024 11:26
@kodiakhq kodiakhq bot merged commit 83741a0 into main May 30, 2024
111 checks passed
@kodiakhq kodiakhq bot deleted the trek/zero-2076-update-node-16-deprecation-message-to-reference-new-end-of branch May 30, 2024 15:24
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
Labels
pr: automerge Automatically merge the PR when checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants