You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
node v18 support is dropped because it is end of life
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**
After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
node v18 support is dropped because it is end of life
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**
After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
node v18 support is dropped because it is end of life
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**
After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
node v18 support is dropped because it is end of life
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**
After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
node v18 support is dropped because it is end of life
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**
After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
node v18 support is dropped because it is end of life
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**
Constructing classes like IncomingMessage or ServerResponse without the new
keyword is now discouraged. This clarifies API expectations and aligns with standard
JavaScript behavior. It may warn or error in future versions.
Using an empty string for shell previously had undefined behavior. This change
encourages explicit choices (e.g., shell: true or a shell path) and avoids
relying on implementation quirks.
Contributed by Antoine du Hamel and Renegade334 #58564.
HTTP/2 priority signaling
The HTTP/2 prioritization API (e.g., stream.priority) is now deprecated due to
poor real-world support. Applications should avoid using priority hints and expect future removal.
Contributed by Matteo Collina and Antoine du Hamel #58313.
✅ Features graduated to stable
assert.partialDeepStrictEqual()
This method compares only a subset of properties in deep object comparisons,
useful for flexible test assertions. Its stabilization means it's now safe for
general use and won't change unexpectedly in future releases.
🔧 fs.Dir now supports explicit resource management
This improves ergonomics around async iteration of directories. Developers can
now manually control when a directory is closed using .close() or with Symbol.asyncDispose.
🔐 Permissions: implicit allow-fs-read to entrypoint
Node.js permissions model now allows read access to the entry file by default.
It makes running permission-restricted apps smoother while preserving security.
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
If you want to rebase/retry this PR, check this box
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
0.5.0->0.5.12.27.7->2.29.729.5.12->30.0.0v4->v5v4->v5v4->v5v4.3->v4.629.7.0->30.2.08.1.7->9.0.020->2216->2218->223.3.3->3.6.229.2.3->29.4.45.5.4->5.9.3Release Notes
changesets/changesets (@changesets/changelog-github)
v0.5.1Compare Source
Patch Changes
84a4a1b]:actions/checkout (actions/checkout)
v5Compare Source
actions/setup-node (actions/setup-node)
v5Compare Source
codecov/codecov-action (codecov/codecov-action)
v5Compare Source
What's Changed
codecov-cliversion reference example by @webknjaz in #1774Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1
creyD/prettier_action (creyD/prettier_action)
v4.6Compare Source
What's Changed
New Contributors
Full Changelog: creyD/prettier_action@v4.5...v4.6
v4.5Compare Source
What's Changed
Full Changelog: creyD/prettier_action@v4.4...v4.5
v4.4Compare Source
What's Changed
Thanks a lot to you all!
New Contributors
Full Changelog: creyD/prettier_action@v4.3...v4.4
jestjs/jest (jest)
v30.2.0Compare Source
Chore & Maintenance
[*]Update example repo for testing React Native projects (#15832)[*]Updatejest-watch-typeaheadto v3 (#15830)v30.1.3Compare Source
Fixes
unstable_mockModulewithnode:prefixed core modules.v30.1.2Compare Source
v30.1.1Compare Source
Fixes
[jest-snapshot-utils]Fix deprecated goo.gl snapshot warning not handling Windows end-of-line sequences (#15800)v30.1.0Compare Source
v30.0.5Compare Source
v30.0.4Compare Source
Features
[expect]TheInversetype is now exported (#15714)[expect]feat: supportasync functionsintoBe(#15704)Fixes
[jest]jest --onlyFailures --listTests now correctly lists only failed tests (#15700)[jest-snapshot]Handle line endings in snapshots (#15708)v30.0.3Compare Source
Fixes
[jest-config]Fix ESM TS config loading in a CJS project (#15694)Features
[jest-diff]Show non-printable control characters to diffs (#15696)v30.0.2Compare Source
v30.0.1Compare Source
v30.0.0Compare Source
lerna/lerna (lerna)
v9.0.0Compare Source
Bug Fixes
Features
OIDC trusted publishing is now supported by Lerna with no specification configuration required.
BREAKING CHANGES
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule
The versions of node supported by lerna are now
^20.19.0 || ^22.12.0 || >=24.0.0.If you are still using
lerna add,lerna bootstraporlerna linkcommands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**8.2.4 (2025-07-27)
Bug Fixes
8.2.3 (2025-06-29)
Bug Fixes
8.2.2 (2025-04-10)
Note: Version bump only for package lerna
8.2.1 (2025-03-03)
Note: Version bump only for package lerna
v8.2.4Compare Source
Bug Fixes
Features
OIDC trusted publishing is now supported by Lerna with no specification configuration required.
BREAKING CHANGES
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule
The versions of node supported by lerna are now
^20.19.0 || ^22.12.0 || >=24.0.0.If you are still using
lerna add,lerna bootstraporlerna linkcommands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**8.2.4 (2025-07-27)
Bug Fixes
8.2.3 (2025-06-29)
Bug Fixes
8.2.2 (2025-04-10)
Note: Version bump only for package lerna
8.2.1 (2025-03-03)
Note: Version bump only for package lerna
v8.2.3Compare Source
Bug Fixes
Features
OIDC trusted publishing is now supported by Lerna with no specification configuration required.
BREAKING CHANGES
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule
The versions of node supported by lerna are now
^20.19.0 || ^22.12.0 || >=24.0.0.If you are still using
lerna add,lerna bootstraporlerna linkcommands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**8.2.4 (2025-07-27)
Bug Fixes
8.2.3 (2025-06-29)
Bug Fixes
8.2.2 (2025-04-10)
Note: Version bump only for package lerna
8.2.1 (2025-03-03)
Note: Version bump only for package lerna
v8.2.2Compare Source
Bug Fixes
Features
OIDC trusted publishing is now supported by Lerna with no specification configuration required.
BREAKING CHANGES
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule
The versions of node supported by lerna are now
^20.19.0 || ^22.12.0 || >=24.0.0.If you are still using
lerna add,lerna bootstraporlerna linkcommands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**8.2.4 (2025-07-27)
Bug Fixes
8.2.3 (2025-06-29)
Bug Fixes
8.2.2 (2025-04-10)
Note: Version bump only for package lerna
8.2.1 (2025-03-03)
Note: Version bump only for package lerna
v8.2.1Compare Source
Bug Fixes
Features
OIDC trusted publishing is now supported by Lerna with no specification configuration required.
BREAKING CHANGES
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule
The versions of node supported by lerna are now
^20.19.0 || ^22.12.0 || >=24.0.0.If you are still using
lerna add,lerna bootstraporlerna linkcommands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**8.2.4 (2025-07-27)
Bug Fixes
8.2.3 (2025-06-29)
Bug Fixes
8.2.2 (2025-04-10)
Note: Version bump only for package lerna
8.2.1 (2025-03-03)
Note: Version bump only for package lerna
v8.2.0Compare Source
Bug Fixes
Features
OIDC trusted publishing is now supported by Lerna with no specification configuration required.
BREAKING CHANGES
As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.
When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.
We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:
https://github.com/nodejs/release#release-schedule
The versions of node supported by lerna are now
^20.19.0 || ^22.12.0 || >=24.0.0.If you are still using
lerna add,lerna bootstraporlerna linkcommands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**8.2.4 (2025-07-27)
Bug Fixes
8.2.3 (2025-06-29)
Bug Fixes
8.2.2 (2025-04-10)
Note: Version bump only for package lerna
8.2.1 (2025-03-03)
Note: Version bump only for package lerna
v8.1.9Compare Source
Bug Fixes
Features
8.1.9 (2024-10-31)
Bug Fixes
8.1.8 (2024-08-05)
Bug Fixes
8.1.7 (2024-07-21)
Bug Fixes
8.1.6 (2024-07-05)
Bug Fixes
8.1.5 (2024-06-24)
Bug Fixes
8.1.4 (2024-06-09)
Note: Version bump only for package lerna
8.1.3 (2024-05-13)
Bug Fixes
8.1.2 (2024-02-05)
Note: Version bump only for package lerna
8.1.1 (2024-02-05)
Note: Version bump only for package lerna
v8.1.8Compare Source
Bug Fixes
Features
8.1.9 (2024-10-31)
Bug Fixes
8.1.8 (2024-08-05)
Bug Fixes
8.1.7 (2024-07-21)
Bug Fixes
8.1.6 (2024-07-05)
Bug Fixes
8.1.5 (2024-06-24)
Bug Fixes
8.1.4 (2024-06-09)
Note: Version bump only for package lerna
8.1.3 (2024-05-13)
Bug Fixes
8.1.2 (2024-02-05)
Note: Version bump only for package lerna
8.1.1 (2024-02-05)
Note: Version bump only for package lerna
nodejs/node (node)
v22.20.0Compare Source
v22.19.0Compare Source
v22.18.0Compare Source
v22.17.1Compare Source
v22.17.0: 2025-06-24, Version 22.17.0 'Jod' (LTS), @aduh95Compare Source
Notable Changes
Instantiating
node:httpclasses withoutnewConstructing classes like
IncomingMessageorServerResponsewithout thenewkeyword is now discouraged. This clarifies API expectations and aligns with standard
JavaScript behavior. It may warn or error in future versions.
Contributed by Yagiz Nizipli in #58518.
options.shell = ""innode:child_processUsing an empty string for
shellpreviously had undefined behavior. This changeencourages explicit choices (e.g.,
shell: trueor a shell path) and avoidsrelying on implementation quirks.
Contributed by Antoine du Hamel and Renegade334 #58564.
HTTP/2 priority signaling
The HTTP/2 prioritization API (e.g.,
stream.priority) is now deprecated due topoor real-world support. Applications should avoid using priority hints and expect future removal.
Contributed by Matteo Collina and Antoine du Hamel #58313.
✅ Features graduated to stable
assert.partialDeepStrictEqual()This method compares only a subset of properties in deep object comparisons,
useful for flexible test assertions. Its stabilization means it's now safe for
general use and won't change unexpectedly in future releases.
Contributed by Ruben Bridgewater in #57370.
Miscellaneous
dirent.parentPathfilehandle.readableWebStream()fs.glob()fs.openAsBlob()node:readline/promisesport.hasRef()readable.compose()readable.iterator()readable.readableAbortedreadable.readableDidReadDuplex.fromWeb()Duplex.toWeb()Readable.fromWeb()Readable.isDisturbed()Readable.toWeb()stream.isErrored()stream.isReadable()URL.createObjectURL()URL.revokeObjectURL()v8.setHeapSnapshotNearHeapLimit()Writable.fromWeb()Writable.toWeb()writable.writableAbortedERR_INPUT_TYPE_NOT_ALLOWEDERR_UNKNOWN_FILE_EXTENSIONERR_UNKNOWN_MODULE_FORMATERR_USE_AFTER_CLOSEContributed by James M Snell in
#57513 and
#58541.
Semver-minor features
🔧
fs.FileHandle.readableWebStreamgetsautoCloseoptionThis gives developers explicit control over whether the file descriptor should
be closed when the stream ends. Helps avoid subtle resource leaks.
Contributed by James M Snell in #58548.
🔧
fs.Dirnow supports explicit resource managementThis improves ergonomics around async iteration of directories. Developers can
now manually control when a directory is closed using
.close()or withSymbol.asyncDispose.Contributed by Antoine du Hamel in #58206.
📊
http2gains diagnostics channel:http2.server.stream.finishAdds observability support for when a stream finishes. Useful for logging,
monitoring, and debugging HTTP/2 behavior without patching internals.
Contributed by Darshan Sen in #58560.
🔐 Permissions: implicit allow-fs-read to entrypoint
Node.js permissions model now allows read access to the entry file by default.
It makes running permission-restricted apps smoother while preserving security.
Contributed by Rafael Gonzaga in #58579.
🎨
util.styleText()adds'none'styleThis lets developers remove styling cleanly without hacks. Useful for overriding
inherited terminal styles when composing styled strings.
Contributed by James M Snell in #58437.
🧑💻 Community updates
0105c13556] - doc: add Filip Skokan to TSC (Rafael Gonzaga) #584993b857735ef] - doc: add JonasBa to collaborators (Jonas Badalic) #58355fdf7612735] - doc: add puskin to collaborators (Giovanni Bucci) #58308Commits
ffe7e1ace0] - (SEMVER-MINOR) assert: mark partialDeepStrictEqual() as stable (Ruben Bridgewater) #57370269931f289] - async_hooks: ensure AsyncLocalStore instances work isolated (Gerhard Stöbich) #581499e0746a4ff] - benchmark: fix broken fs.cpSync benchmark (Dario Piotrowicz) #58472dee8cb5bcb] - benchmark: add more options to cp-sync (Sonny) #58278e840fd5b85] - benchmark: fix typo in method name for error-stack (Miguel Marcondes Filho) #58128b9a16e97e0] - buffer: give names toBuffer.prototype.*Write()functions (Livia Medeiros) #58258d56a5e40af] - buffer: use constexpr where possible (Yagiz Nizipli) #58141215587feca] - build: add support for OpenHarmony operating system (hqzing) #583509bcef6821c] - build: fix uvwasi pkgname (Antoine du Hamel) #582707c3883c2ae] - build: search for libnode.so in multiple places (Jan Staněk) #582133f954accb3] - build: fix pointer compression builds (Joyee Cheung) #5817104c8f59f84] - build: use FILE_OFFSET_BITS=64 esp. on 32-bit arch (RafaelGSS) [#58090](https://redirect.github.com/nodejs/node/pull/5809Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.