Takashi Sato

The current code still does not work properly in the case that multiple files are edited at the same time and one or more files are updated in a formatted...

I agree with @privatenumber . Since this branch is very old and differs significantly from the latest master, I forked this action and [implemented an option to install a self-contained...

@fz6m > I think adding a `node-version` option, detect it and auto switch `pnpm@version` to `@pnpm/exe@version` is better. That is a nice feature, but a bit complicated. I may try...

After thinking about how to implement this feature, I gave up trying to implement it. The `node-version` option of [setup-node](https://github.com/actions/setup-node) can take various values. For example, "^18.0.0", ">=18.0.0", "lts/*", etc....

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

I specified a pnpm version in `package.json` ``` "packageManager": "[email protected]", ``` and it works fine with pnpm/action-setup. Note that [email protected] + Node.js 14 does not work fine but this is...