New release request

[MikeMcC399]

Please cut a new release of Corepack and pass it on to the Node.js bundling process for currently supported versions.

• 77fff3c disabled auto-pinning. This is a very useful change and can help prevent mistaken accidental changes to package.json. (PR Disables auto-pinning by default #709).

• Also please merge the changes from feat: update package manager versions #671. Currently yarn dlx uses yarn@4.6.0, ignoring any other Yarn version that is globally installed in Corepack, due to issue Why do Yarn "transparent" commands use hardcoded versions? #202

[MikeMcC399]

Are there any active maintainers who can respond?

[arcanis]

Yes, I'm taking a look at this.

[MikeMcC399]

@arcanis

Yes, I'm taking a look at this.

Thank you very much!

I wasn't sure what was happening with the maintenance of Corepack, since there has been only sporadic maintenance activity following the Node.js TSC decision in March 2025 not to bundle Corepack in Node.js 25 and above. There haven't been any new releases since then. The last release was 0.32.0 on Feb 28, 2025, before the vote was completed.

From my point of view, even if there are no major changes planned for Corepack, it would be great to keep it maintained to continue to support Yarn Modern, where it is still the recommended prerequisite.

[MikeMcC399]

@arcanis

Yes, I'm taking a look at this.

Did you make any progress after looking at this issue?

[arcanis]

I thought the release would be made automatically on merge; fixed with the 0.33 release

[MikeMcC399]

@arcanis

I thought the release would be made automatically on merge; fixed with the 0.33 release

Thank you!

You might want to manually add PR #709 into the release notes

https://github.com/nodejs/corepack/releases/tag/v0.33.0

as otherwise it won't be so obvious that the default for COREPACK_ENABLE_AUTO_PIN is now set to 0 (disabled)