docs(README): update version

Author: zkochan

README.md

@@ -5,7 +5,7 @@ Install pnpm **and** a JavaScript runtime (Node.js, Bun, or Deno) in a single Gi
 pnpm ships a self-contained release binary — the action downloads it for the runner's platform from the npm registry, refusing anything whose npm signature or checksum does not check out (no Node.js or npm needed) and then uses `pnpm runtime set` to install the requested runtime. The runtime binary is placed on `PATH` for subsequent steps, replacing the need for `actions/setup-node`, `oven-sh/setup-bun`, or `denoland/setup-deno`. `pnpm install` runs automatically when a `package.json` is present.
 
 > [!NOTE]
-> `pnpm/setup@v2` installs pnpm v11 and newer only — it relies on pnpm's self-contained release binaries and the `pnpm runtime` command, both available from v11. `v1` installed pnpm through npm and could set up pnpm 10; if you need pnpm 10 or older, use [`pnpm/action-setup`](https://github.com/pnpm/action-setup) instead.
+> `pnpm/setup@v3` installs pnpm v11 and newer only — it relies on pnpm's self-contained release binaries and the `pnpm runtime` command, both available from v11. `v1` installed pnpm through npm and could set up pnpm 10; if you need pnpm 10 or older, use [`pnpm/action-setup`](https://github.com/pnpm/action-setup) instead.
 >
 > One caveat: pnpm v11 publishes no binary for Intel macOS (`darwin-x64`); use v12 or newer on Intel macOS runners.
 
@@ -64,7 +64,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v7
-      - uses: pnpm/setup@v2
+      - uses: pnpm/setup@v3
       - run: node --version
       - run: pnpm test
 ```
@@ -77,7 +77,7 @@ With a `.node-version`, `.nvmrc`, or Node.js entry in `.tool-versions` in the
 project directory, no runtime input is needed:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
 ```
 
 Node.js version selection uses this precedence:
@@ -96,15 +96,15 @@ another file. If no version source exists, Node.js is not installed unless
 To use a different file:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     node-version-file: config/node-version
 ```
 
 To disable version-file detection:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     node-version-file: false
 ```
@@ -133,7 +133,7 @@ jobs:
         node: [22, 24, 26]
     steps:
       - uses: actions/checkout@v7
-      - uses: pnpm/setup@v2
+      - uses: pnpm/setup@v3
         with:
           runtime: node@${{ matrix.node }}
       - run: pnpm test
@@ -142,11 +142,11 @@ jobs:
 ### Install Bun or Deno
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     runtime: bun@latest
 
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     runtime: deno@2
 ```
@@ -157,7 +157,7 @@ When the project is not at the repository root — a site in `docs/`, an app in
 `web/` — point the action at it:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     working-directory: docs
     cache: true
@@ -180,7 +180,7 @@ the project's own root is not the repository root.
 ### Cache the pnpm store
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     cache: true
 ```
@@ -234,7 +234,7 @@ known to be complete. The record count cannot be bounded there, so only the
 ### Require a lockfile
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     require-lockfile: true
 ```
@@ -278,7 +278,7 @@ and tokens together. Use YAML's `|` block to keep the JSON readable. For
 example, to install `@myorg/*` packages from GitHub Packages:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   env:
     pnpm_config__auth: |
       {
@@ -294,7 +294,7 @@ Use `"@"` for a registry-wide default token. This also selects that URL as the
 default registry:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   env:
     pnpm_config__auth: |
       {
@@ -319,7 +319,7 @@ See pnpm's [`_auth` documentation](https://pnpm.io/npmrc#_auth) for details.
 For jobs that only need pnpm itself — e.g. `pnpm audit`, lockfile-only regeneration — set `install: false`:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   with:
     install: false
 - run: pnpm audit
@@ -339,7 +339,7 @@ pnpm 12 links global runtime bins as context-aware shims: running `node` inside
 So whenever the action installs a runtime, it exports `PNPM_CONFIG_GLOBAL_SHIMS` with that runtime disabled (`{"node":false}`), leaving every other runtime at pnpm's defaults. To keep the switching behaviour, set the variable yourself — the action never overwrites a value the workflow already provides:
 
 ```yaml
-- uses: pnpm/setup@v2
+- uses: pnpm/setup@v3
   env:
     PNPM_CONFIG_GLOBAL_SHIMS: '{"node":"auto"}'
   with: