Skip to content

[Node Agent] Bump node major version to 22 #742

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

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 30, 2024

Bumps the node docker images versions

[node-agent] Bump node version in dockerfiles/maven/Dockerfile

changed lines [2] of file "/tmp/updatecli/github/jenkins-docs/quickstart-tutorials/dockerfiles/node/Dockerfile"

22
Release published on the 2024-10-29 15:11:08 +0000 UTC at the url https://github.com/nodejs/node/releases/tag/v22.11.0

### Notable Changes

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

Other than updating metadata, such as the `process.release` object, to reflect
that the release is LTS, no further changes from Node.js 22.10.0 are included.

### OpenSSL 3.x

Official binaries for Node.js 22.x currently include OpenSSL 3.0.x (more
specifically, the [quictls OpenSSL fork](https://github.com/quictls/openssl)).
OpenSSL 3.0.x is the currently designated long term support version that is
scheduled to be supported until 7th September 2026, which is within the expected
lifetime of Node.js 22.x. We are expecting upstream OpenSSL to announce a
successor long term support version prior to that date and since OpenSSL now
follows a semantic versioning-like versioning scheme we expect to be able to
update to the next long term supported version of OpenSSL during the lifetime of
Node.js 22.x.
GitHub Action workflow link
Updatecli logo

Created automatically by Updatecli

Options:

Most of Updatecli configuration is done via its manifest(s).

  • If you close this pull request, Updatecli will automatically reopen it, the next time it runs.
  • If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made.

Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

@github-actions github-actions bot added the dependencies Pull requests that update a dependency file label Oct 30, 2024
@github-actions github-actions bot force-pushed the updatecli_weekly_651f9b43b3cb77399a9a3a2acf5f7cb4b5cbafd0c8a53ccf4e8e1ec8b505fbf6 branch from 00dee98 to 21fcc4d Compare October 30, 2024 16:53
@gounthar gounthar merged commit b7e4c14 into weekly Oct 30, 2024
10 checks passed
@gounthar gounthar deleted the updatecli_weekly_651f9b43b3cb77399a9a3a2acf5f7cb4b5cbafd0c8a53ccf4e8e1ec8b505fbf6 branch October 30, 2024 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file nodejs repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant