-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
doc: clarify Corepack removal in v25+ #57813
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with the grammar suggestion
The commit message do not match our guidelines, the first word after the subsystem should be an imperative verb. |
Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
f163dc7
to
3b95127
Compare
@aduh95 I've updated the first commit to use imperative verb after subsystem: |
Closing this PR, as the existing documentation can be edited better with highlight and call to action just like it's done for other modules for all Node.js versions. That PR is posted in #57825 |
I'll post a new PR specific to v25.x after #57825 is merged. |
We're instead trying to enable redirect from corepack latest documentation in nodejs/nodejs.org#7643 (review) |
Alternative to #57663
This preserves the existing documentation page for corepack which has backlinks from all over the internet.
It can be removed close to April 2028, after corepack is completely removed from all Node.js versions.
Refs: