Skip to content

doc: explicitly state that corepack will be removed in v25+ #57747

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

Merged
merged 2 commits into from
Apr 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/api/corepack.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,6 @@ Documentation for this tool can be found on the [Corepack repository][].

Despite Corepack being distributed with default installs of Node.js, the package
managers managed by Corepack are not part of the Node.js distribution, and
Corepack itself will no longer be distributed with future versions of Node.js.
Corepack itself will no longer be distributed with Node.js 25+.
Copy link

@MikeMcC399 MikeMcC399 Apr 5, 2025

Choose a reason for hiding this comment

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

@trivikr

I'll just remove the v as of now, and will wait for input from other collaborators

Using the notation from https://github.com/nodejs/release including the use of the term "release line" to refer to all releases with same major version number:

Suggested change
Corepack itself will no longer be distributed with Node.js 25+.
Corepack itself will no longer be distributed with release lines Node.js 25 and above.

You could also write "releases Node.js >=25.0.0" using semver notation.


[Corepack repository]: https://github.com/nodejs/corepack
Loading