Repository navigation
Corepack Support #531
Description
Activity
Hello @RichiCoder1. Thank you for your feature request. Actually we had similar proposal to enable corepack by default. I think we should reinvestigate adding corepack support. We'll ping you about its results.
Reacted by Marius Butuc and anton-zano@dmitry-shibanov apologies for not seeing that closed ticket! I very much hope ya'll do. While technically experimental, it's being officially recommended and there's no (current) way to use both this action and corepack without some awkward contortions. Looking forward to the outcome!
I use corepack locally and hope we can integrate it with GitHub Actions :)
If I'm understanding correctly, right now you can run
setup-node, set up Corepack, and then run the standalonecacheaction. So is the benefit of this just to be able to do it all inside thesetup-nodeaction?Reacted by Ilia TsvetkovI don't know either, I was just summarizing my understanding from the issue description.
The semi-simple way w/ caching and something like pnpm would be:
- run: corepack enable - uses: actions/setup-node@v3 with: node-version: 16 cache: pnpm - run: pnpm i
I think that may be faintly fragile as
corepack enableoperates on the built in node and not the potentially installed one. It does however fix an issue wheresetup-nodewill look for apnpmexe/cache that doesn't exist yet when setting up cache I think.Reacted by Wout Mertens, Emilio Martinez, Marius Butuc, Fernando Pasik and helle253Reacted by Steven and Fernando Pasik@brcrista and your understanding is correct. Ideally with some extra smarts enabled by knowing exactly which packageManager is in use.
@RichiCoder1 thanks for you notification, it was a good point to review, but we should not go ahead of nodejs team and turn on corepack by default while it is not default for the nodejs itself.
The consequences of having corepack enabled are risky for some builds and adding new input is not necessary complication of the action and its documentation.
In the current state of the corepack to have an explicit simple step enabling the feature seems to be optimal solution.I have to reject the feature request and close the issue, but please feel free to reopen it or create new one in case you still have some problems.
Reacted by Jarrod Davis, Tetsuro Higuchi, Steven, Daniel Bayley, Ranieri Althoff, Konstantin Tarkus, Chris Weed, Mark H, Andrey (Andrii) Los, Grigory and 16 moreReacted by Hugo Alliaume, Jackson Blankenship, Simon Lepel, yarinsa, Josh Wooding, Wout Mertens, Nwel, Tetsuro Higuchi, Steven, Mark H and 5 moreThat's unfortunate; I avoid using the cache feature of the action because I'm nervous of mixing different major npm versions' caches. Having a corepack opt-in would compose well there, but I guess I'll just keep using the 4 steps (!) of setup-node, enable corepack, get cache location, cache, or keep mixing the npm version into the cache key.
Reacted by Simon Lepel65 remaining items
And while I'm downvoted into oblivion
The downvotes aren't because of the provided solution's ineffectiveness (it works) but because of setup-node inability to properly address it.
Reacted by Avasam, Jake Hiller, Oleksandr Danylchenko, Adam Haglund, Matei Trandafir, helle253, Eduardo Sanchez and William EntrikenThanks, @fulldecent. The following solution worked for my
npmsetup:- name: Setup Node.js uses: actions/setup-node@v6 with: node-version-file: .nvmrc registry-url: "https://registry.npmjs.org" scope: "..." - name: Enable Corepack shell: bash run: corepack enable npm - name: Enable NPM cache uses: actions/setup-node@v6 with: cache: npm
However, what would be the recommended approach for supporting Node 25 in the future?
It won't supply thecorepackanymore. So should I explicitly add thenpm i -g corepackbefore thecorepack enable npm?Reacted by William Entriken- added a commit that references this issue
on Feb 11, 2026 - added a commit that references this issue
on Feb 20, 2026 I would say that even after all these years, I still oppose adding configuration support for corepack to
actions/setup-node. Corepack is not actively maintained and is no longer built into NodeJS.Reacted by Martin Adámek, Daniil Suvorov, Yaroslav Admin, Oleksandr Danylchenko, Joe, Filip Malinowski, Sʜɪᴍᴜʀᴀ Yū, Eduardo Sanchez, Mikey O'Toole, Nelson Martell and 3 moreCorepack is not actively maintained
This statement is incorrect.
- Contribution graph: https://github.com/nodejs/corepack/graphs/contributors
- A version was published last week https://github.com/nodejs/corepack/releases/tag/v0.35.0
- It also reduced install size by 43%
- corepack still has 4M weekly downloads and rising https://npmx.dev/package/corepack
Reacted by Filip Malinowski, Sʜɪᴍᴜʀᴀ Yū, Eli, Brian Kidd, Eduardo Sanchez, Chris Nielsen, Simon Rolland and Noah SherwinReacted by Nikolai Røed Kristiansen, Christian Bewernitz, Daniil Suvorov, Oleksandr Danylchenko, Yaroslav Admin, Joe, Filip Malinowski, Steven, Eli, Brian Kidd and 2 moreCorepack is not actively maintained
This statement is incorrect.
-
Contribution graph: https://github.com/nodejs/corepack/graphs/contributors
-
A version was published last week https://github.com/nodejs/corepack/releases/tag/v0.35.0
- It also reduced install size by 43%
-
corepack still has 4M weekly downloads and rising https://npmx.dev/package/corepack
According to the decision made in pnpm/pnpm#11732 (comment) , the pnpm community has essentially removed pnpm's support for corepack. I don't see any point in pretending that corepack is still compatible with third-party package managers within its git repository.
-
Not only the pnpm community. Yarn as well, they have their new official version switcher: https://v6.yarnpkg.com/concepts/switch
Please, do not use corepack to install pnpm.
Reacted by Nathan Moin Vaziri, Eli, William Entriken, Ben Quarmby and StevenNow that actions/setup-node@v7 is released, Yarn works for me (including cache) with @ildella's approach:
This should solve @xenoterracide's issue above, and @cowwoc's double setup-node workaround, which was previously best practice.
# Update this when Yarn no longer recommends Corepack # See: https://yarnpkg.com/getting-started/install - name: Enable Corepack run: corepack enable - name: Setup Node.js uses: actions/setup-node@v7 with: node-version-file: .node-version cache: yarn cache-dependency-path: yarn.lock - name: Install dependencies run: yarn install --immutable
I now maintain a repo just for integration testing how Yarn installs on GitHub Actions.
@oleksandr-danylchenko even though Node.js soon (i.e. next LTS) drops support and pnpm/Yarn deprecate corepack, there is no plan for GitHub runners to drop corepack. It would be responsible if they support corepack at least until actions/setup-node supports all the next generation solutions from these respective package managers.
Reacted by Avasam and Daniele Dellafiore- added a commit that references this issue
on Sep 8, 2026
Description:
Support using https://github.com/nodejs/corepack to manage non-NPM package managers.
Ideally in between installing node and bootstrapping the package manager cache, this action:
corepack prepare --active(after some research, that last one may not necessary but instead makes an implicit step explicit)
This behavior could either be trigged by the presence of the
packageManagerfield in the rootpackage.json(might be suprising),cache: 'auto'as possibly envisioned in #306, orcorepack: trueJustification:
Both pnpm and yarn support corepack, and yarn recommendeds corepack for package manager versioning. Currently using corepack with this action will break when using the
cachekey as this action assumes the appropriate version manager has already been installed. However, you don't necessarily want to bootstrap with corepack until the appropriate node version has been installed and configured.Related: #530 #182
Are you willing to submit a PR?
Yes