-
-
Notifications
You must be signed in to change notification settings - Fork 205
New release request #713
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
Comments
Are there any active maintainers who can respond? |
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. |
Uh oh!
There was an error while loading. Please reload this page.
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[email protected]
, ignoring any other Yarn version that is globally installed in Corepack, due to issue Why do Yarn "transparent" commands use hardcoded versions? #202The text was updated successfully, but these errors were encountered: