Mike McCready

@gert-janvercauteren The example workflow in the documentation section https://docs.cypress.io/accessibility/results-api#Example-Job-Workflow-Update on the page [Accessibility > Results API](https://docs.cypress.io/accessibility/results-api) that you reference does not use the action `cypress-io/github-action` (see below for a copy),...

Open issues should be reviewed to determine if any are blockers to declaring Corepack "production-ready" ~~@arcanis already suggested #485~~ Edit: resolved

https://github.com/nodejs/corepack/issues/616 also seems like it ought to be defined as a blocker. The related PR https://github.com/nodejs/corepack/pull/647 looks like it has stalled waiting for maintainer feedback.

#202 should also be fixed. Without a fix, stored package manager versions are used, based on whatever version was current at the time of a Corepack release, instead of using...

@arcanis > I'd suggest to disable auto-pinning before tagging 1.0 stable. Thanks for disabling this in [[email protected]](https://github.com/nodejs/corepack/releases/tag/v0.33.0)! One less blocker for a production-ready release!

Could the maintainers please respond about their plans for this repo? It seems that there is now very little activity. PR https://github.com/nodejs/corepack/pull/647 is stalled and there are several new issues...

@arcanis Thanks for explaining your bandwidth constraints! That does however seem to leave a gap unless there are going to be other active maintainers looking after the interests of npm...

@trivikr Nothing has changed since my previous https://github.com/nodejs/corepack/issues/681#issuecomment-2829546843. My bandwidth is also taken up with other repos that I maintain, and since one of those repos depends on Corepack this...

@trivikr > Should we provide a summary I'm not sure how you would summarize the status better than the response in https://github.com/nodejs/corepack/issues/687#issuecomment-3025544220 The status doesn't seems to fit well into...

The workaround is to use [actions/setup-node](https://github.com/actions/setup-node) to install a supported version of Node.js