doc: clarify future Corepack removal in v25+ #57825
Merged
Conversation
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
MikeMcC399
reviewed
Apr 10, 2025
ljharb
approved these changes
Apr 10, 2025
trivikr
commented
Apr 10, 2025
marco-ippolito
approved these changes
Apr 11, 2025
5 tasks
trivikr
commented
Apr 11, 2025
aduh95
added
the
dont-land-on-v24.x
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
trivikr
removed
the
dont-land-on-v24.x
This comment was marked as resolved.
This comment was marked as resolved.
trivikr
added
the
dont-land-on-v24.x
This comment was marked as resolved.
This comment was marked as resolved.
RaisinTen
approved these changes
Apr 13, 2025
UlisesGascon
approved these changes
Apr 13, 2025
Co-authored-by: Darshan Sen <[email protected]>
jasnell
approved these changes
Apr 13, 2025
aduh95
reviewed
Apr 13, 2025
aduh95
approved these changes
Apr 13, 2025
Co-authored-by: Antoine du Hamel <[email protected]>
aduh95
added
author ready
RaisinTen
approved these changes
Apr 14, 2025
trivikr
added
the
commit-queue-squash
trivikr
added
the
commit-queue
nodejs-github-bot
removed
the
commit-queue
|
Landed in 004ecc1 |
trivikr
removed
the
commit-queue-squash
|
This didn't find its way into the Node.js v22.15.0 release today and the current statement could be interpreted to mean that Corepack will no longer be distributed with future versions of Node.js 22.x
|
RafaelGSS
pushed a commit
that referenced
this pull request
May 1, 2025
PR-URL: #57825 Reviewed-By: Jordan Harband <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
aduh95
pushed a commit
that referenced
this pull request
May 8, 2025
PR-URL: #57825 Reviewed-By: Jordan Harband <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #57747
This highlights the removal, and gives a call to action for existing users.
This is similar to the documentation for punycode https://nodejs.org/api/punycode.html