v4.0.0

v4.0.0

BREAKING CHANGE

Update to pnpm/action-setup@v4.

The default value of the pnpm input has been changed from the value 9 to null because of following changes in pnpm/action-setup@v4:

An error is thrown if one version of pnpm is specified in the packageManager field of package.json and a different version is specified in the action's settings.

Meaning, if setup-node-pnpm always provides a default value to the pnpm version input, you could never use the packageManager version of package.json

Therefore, we now also support the package_file input for the packageManager value.

What to do, now?

There are two scenarios.

1. You want to use the pnpm version specified in your package.json packageManager field:

   {
     ...
     "packageManager": "pnpm@10.7.1",
     ...
   }

   Now you can use the action without a pnpm input.

   - uses: dafnik/setup-node-pnpm@v4

2. You don't want to use the package.json packageManager field:

   - uses: dafnik/setup-node-pnpm@v4
     with:
       pnpm: 10

📖 Docs

• docs: update everything around the action @Dafnik (#28)
• feat: add COC, issue templates, FUNDING.yml, dev ci @Dafnik (#26)
• docs: update SECURITY.md @Dafnik (#25)

🧰 Maintenance

• chore: update pnpm/action-setup @Dafnik (#32)
• chore: update pnpm/action-setup action to v4 @renovate[bot] (#31)
• chore: move renovate.json config into .github folder @Dafnik (#30)
• build(config): migrate renovate config @renovate[bot] (#29)
• chore: update dependency prettier to v3.3.2 @renovate[bot] (#27)

See details of all code changes since previous release.