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

v16.13.0 release proposal #40536

Merged
merged 1 commit into from
Oct 26, 2021
Merged

v16.13.0 release proposal #40536

merged 1 commit into from
Oct 26, 2021

Conversation

richardlau
Copy link
Member

@richardlau richardlau commented Oct 20, 2021

2021-10-26, Version 16.13.0 'Gallium' (LTS), @richardlau

Notable Changes

This release marks the transition of Node.js 16.x into Long Term Support (LTS)
with the codename 'Gallium'. The 16.x release line now moves into "Active LTS"
and will remain so until October 2022. After that time, it will move into
"Maintenance" until end of life in April 2024.


cc @nodejs/lts

Generated via git node release --prepare --startLTS with nodejs/node-core-utils#573 with the commits section removed (no commits other than the release commit).

@nodejs-github-bot nodejs-github-bot added meta Issues and PRs related to the general management of the project. needs-ci PRs that need a full CI run. v16.x labels Oct 20, 2021
Notable changes:

This release marks the transition of Node.js 16.x into Long Term Support (LTS)
with the codename 'Gallium'. The 16.x release line now moves into "Active LTS"
and will remain so until October 2022. After that time, it will move into
"Maintenance" until end of life in April 2024.

PR-URL: #40536
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@VoltrexKeyva VoltrexKeyva removed the needs-ci PRs that need a full CI run. label Oct 25, 2021
Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Mesteery Mesteery added release Issues and PRs related to Node.js releases. and removed meta Issues and PRs related to the general management of the project. labels Oct 25, 2021
Copy link
Contributor

@DerekNonGeneric DerekNonGeneric left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

richardlau added a commit that referenced this pull request Oct 26, 2021
@richardlau richardlau merged commit 40ecd56 into v16.x Oct 26, 2021
richardlau added a commit that referenced this pull request Oct 26, 2021
Notable changes:

This release marks the transition of Node.js 16.x into Long Term Support (LTS)
with the codename 'Gallium'. The 16.x release line now moves into "Active LTS"
and will remain so until October 2022. After that time, it will move into
"Maintenance" until end of life in April 2024.

PR-URL: #40536
richardlau added a commit to richardlau/nodejs.org that referenced this pull request Oct 26, 2021
richardlau added a commit to nodejs/nodejs.org that referenced this pull request Oct 26, 2021
@richardlau richardlau deleted the v16.13.0-proposal branch October 26, 2021 16:54
Trott pushed a commit that referenced this pull request Oct 26, 2021
Update missed changes for the main CHANGELOG.md for Node.js 16.13.0.

PR-URL: #40617
Refs: #40536
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
richardlau added a commit that referenced this pull request Oct 26, 2021
Update missed changes for the main CHANGELOG.md for Node.js 16.13.0.

PR-URL: #40617
Refs: #40536
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
targos pushed a commit that referenced this pull request Nov 6, 2021
Update missed changes for the main CHANGELOG.md for Node.js 16.13.0.

PR-URL: #40617
Refs: #40536
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@antonyggvzvmnxxcx

This comment has been minimized.

@Trott Trott mentioned this pull request Nov 22, 2021
1 task
DerekNonGeneric added a commit to OpenINF/openinf-util-types that referenced this pull request Aug 23, 2022
* Begin specifying the Last Known Good Release of Node.js toolchain,
   which is the 1ˢᵗ version of the “Gallium” LTS release line.

Refs: nodejs/node#40536 (review)

> This release marks the transition of Node.js 16.x into Long Term
> Support (LTS) with the codename “Gallium”. The 16.x release line
> now moves into “Active LTS” and will remain so until October 2022.
> After that time, it will move into “Maintenance” until end-of-life
> in April 2024.

Refs: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V16.md#16.13.0

* Begin specifying that we would like to use globally-installed npm.

> While `npm` is a valid option in the “packageManager” property, the
> lack of shim will cause the global npm to be used.

Refs: https://nodejs.org/docs/v16.13.0/api/corepack.html#corepack_how_does_corepack_interact_with_npm

> If the value corresponds to a supported package manager, Corepack
> will make sure that all calls to the relevant binaries are run
> against the requested version, downloading it on demand if needed,
> and aborting if it cannot be successfully retrieved.

Refs: https://nodejs.org/docs/v16.13.0/api/corepack.html#configuring-a-package

Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is>
DerekNonGeneric added a commit to OpenINF/openinf-util-md-table that referenced this pull request Aug 23, 2022
* Begin specifying the Last Known Good Release of Node.js toolchain,
  which is the 1ˢᵗ version of the “Gallium” LTS release line.

Refs: nodejs/node#40536 (review)

> This release marks the transition of Node.js 16.x into Long Term
> Support (LTS) with the codename “Gallium”. The 16.x release line
> now moves into “Active LTS” and will remain so until October 2022.
> After that time, it will move into “Maintenance” until end-of-life
> in April 2024.

Refs: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V16.md#16.13.0

* Begin specifying that we would like to use globally-installed npm.

> While `npm` is a valid option in the “packageManager” property, the
> lack of shim will cause the global npm to be used.

Refs: https://nodejs.org/docs/v16.13.0/api/corepack.html#corepack_how_does_corepack_interact_with_npm

> If the value corresponds to a supported package manager, Corepack
> will make sure that all calls to the relevant binaries are run
> against the requested version, downloading it on demand if needed,
> and aborting if it cannot be successfully retrieved.

Refs: https://nodejs.org/docs/v16.13.0/api/corepack.html#configuring-a-package

Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is>
DerekNonGeneric added a commit to OpenINF/openinf-util-md-table that referenced this pull request Aug 23, 2022
- **Begin specifying the Last Known Good Release of Node.js toolchain**

  LKGR of Node.js toolchain is 1ˢᵗ release of “Gallium” LTS (v16.13.0).

  Refs: nodejs/node#40536 (review)

  > This release marks the transition of Node.js 16.x into Long Term
  > Support (LTS) with the codename “Gallium”. The 16.x release line
  > now moves into “Active LTS” and will remain so until October 2022.
  > After that time, it will move into “Maintenance” until end-of-life
  > in April 2024.

  Days until “Gallium” goes into “Maintenance” (October 2022): 8 weeks from now[^1]
  Days until “Gallium” goes EOL (April 2024): 86 weeks from now[^2]

  [^1]: https://www.wolframalpha.com/input?i2d=true&i=third+Tuesday+in+October+of+year+2022
  [^2]: https://www.wolframalpha.com/input?i2d=true&i=third+Tuesday+in+April+of+year+2024

  Refs: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V16.md#16.13.0

- **Begin specifying that we would like to use globally-installed npm**

  > While `npm` is a valid option in the “packageManager” property, the
  > lack of shim will cause the global npm to be used.

  Refs: https://nodejs.org/docs/v16.13.0/api/corepack.html#corepack_how_does_corepack_interact_with_npm

  > If the value corresponds to a supported package manager, Corepack
  > will make sure that all calls to the relevant binaries are run
  > against the requested version, downloading it on demand if needed,
  > and aborting if it cannot be successfully retrieved.

  Refs: https://nodejs.org/docs/v16.13.0/api/corepack.html#configuring-a-package

Signed-off-by: Derek Lewis <DerekNonGeneric@inf.is>
Co-authored-by: deepsource-autofix[bot] <62050782+deepsource-autofix[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Issues and PRs related to Node.js releases.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants