bump corepack to fix freezes

[jakecoffman]

What are you trying to accomplish?

There was some kind of freeze in Corepack that was reproducible if you gave it a registry that would 404:

$ script/dependabot update npm_and_yarn a/b --debug
$ export COREPACK_NPM_REGISTRY=https://npm.pkg.github.com/
$ corepack install npm@8 --global --cache-only
Internal Error: Server answered with HTTP 404 when performing the request to https://npm.pkg.github.com/npm; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at ClientRequest.<anonymous> (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:42205:23)
    at Object.onceWrapper (node:events:633:26)
    at ClientRequest.emit (node:events:518:28)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:702:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:118:17)
    at TLSSocket.socketOnData (node:_http_client:544:22)
    at TLSSocket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
    at Readable.push (node:internal/streams/readable:392:5)

☝️ The process would not exit from there. It just hangs.

I noticed our version was out of date, so bumping it fixed the problem.

Anything you want to highlight for special attention from reviewers?

How will you know you've accomplished your goal?

We should be able to also verify that it fixes the issue in production with a live test.

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[jeffwidman]

Related:

• Update corepack to fix new error after pnpm upgrade #9324

[jakecoffman]

Some interesting Corepack related failures in the Specs. I don't have the time to track those down. Anyone is welcome to pick this up before I can get to it.

[jakecoffman]

@jeffwidman nice, seems like there's now multiple reasons to bump Corepack!

[kbukum1]

Review Tip:
Corepack's newer versions, when installing dependencies locally, may attempt to add the packageManager field to the package.json. Instead of returning the expected version, Corepack sometimes outputs a warning message that includes the version, leading to a malformed version string. This method cleans the version string by extracting the correct semantic version (x.y.z) from the warning or input, ensuring compatibility with Dependabot and related processes.

[kbukum1]

Some interesting Corepack related failures in the Specs. I don't have the time to track those down. Anyone is welcome to pick this up before I can get to it.

Yes. When corepack installing locally it is expecting to have packageManager field and returning warning instead of the version. So I am cleaning up the version to return version instead of the warning which is causing malformed version error.

[rickreyhsig]

Thank you for the updates! The changes look good overall. It would be great to confirm that everything works as expected with the new version handling logic.

[abdulapopoola]

line 67 is also cleaning a version string; can we consolidate?

[kbukum1]

it is also moved.