Release corepack@1.0.0

Is your request related to a problem? Please describe.

On 2025-03-19, the Node.js TSC voted to stop distributing corepack in Node.js v25+

Corepack will continue to be available on npm, but users have to globally install it using npm install -g corepack. If users install it from npm, they don't have to run corepack enable like they have to when using the version distributed through npm.

However, there are users who like corepack to manage their package manager versions and would like to continue globally installing it. There are many sources for this.

• For explicit request, check https://github.com/nodejs/corepack/issues/681
• Comments and reactions to requesting removing experimental status for corepack from Node.js in https://github.com/nodejs/corepack/issues/104 and https://github.com/nodejs/node/issues/50963, while it was open to discussion.
• Increase in npm download counts by 10X to 2M+ per week in early Feb 2025, when there was an issue with npm rotating the keys which affected pnpm installations from corepack.
• The documentation in yarn and pnpm already recommend installing corepack globally from npm.

Many folks in the software industry associate v1.0.0 as stability. There are some who consider everything with 0.x as unstable irrespective of the popularity or usage. As corepack is not going to be distributed though Node.js, the users have to globally install it with npm install -g corepack. Although it doesn't show version, there are some users who might check the latest version on npm and may not install it if it's still 0.x

At the time of comment, the latest version of corepack is v0.32.0. There are enough data points provided above that v1.0.0 can be published. The release of corepack@v1.0.0 will not affect it's experimental status in Node.js core while it's distributed in <=v24.

Describe the solution you'd like

If maintainers think it's ready, please release corepack@v1.0.0 so that the users who associate 0.x with instability will no longer hesitate to install corepack.

If maintainer thinks it's not ready, please use this issue or create a new issue/milestone/label for tracking the v1.0.0 release.

Describe alternatives you've considered

I personally don't have any issue with using corepack while it's 0.x

For folks who do, we can create documentation similar to what other popular tools who're on 0.x have done, like esbuild or ReactNative.

Additional context

This was suggested in https://github.com/nodejs/corepack/issues/104#issuecomment-2746172451

No file, test, or entry point is identified in the issue. Start by reviewing the release request and its linked TSC, Corepack, and Node.js discussions, then confirm the maintainers' decision; done means either publishing corepack@1.0.0 or documenting a concrete tracking plan for that release.