Pnpm 7 support

[gunta]

Checking here I can see the install script is using https://get.pnpm.io/v6.16.js

action-setup/src/install-pnpm/run.ts

Line 25 in 10b4b0b

const response = await fetch('https://get.pnpm.io/v6.16.js')

Given that the latest 7 version is using https://get.pnpm.io/install.sh as the new install script, is there any change for the process? I can see that the new script is very simple and basically downloads the binary from npm.

[nicksrandall]

The caching examples will need to be updated as the store is now in a new location.

[benmccann]

I don't get it. Why do fetch('https://get.pnpm.io/v6.16.js') at all for users who have specified packageManager in the package.json? It'd be nice if that field could be used without first downloading a file from a hardcoded version

[zkochan]

That file is only used to install pnpm. https://get.pnpm.io/v6.16.js will not install pnpm v6.16.

[michaelhays]

FYI, this action is working with pnpm 7 for me, using these steps: https://pnpm.io/continuous-integration#github-actions

[axelboc]

Working for me too with the example on the pnpm website, which uses action/setup-node's built-in caching feature. This repo's README should probably be updated accordingly. I would just add --frozen-lockfile to the dependencies installation step, though, like in this example from action/setup-node.

[tksst]

It seems like this issue should be closed because pnpm/action-setup works fine with pnpm@7 and pnpm@8