test(snap): work around pnpm v11 unlink frozen-lockfile error

pnpm v11 made `pnpm unlink` actually perform a reconciling install
after removing the override from pnpm-workspace.yaml. Under CI=true
the install defaults to --frozen-lockfile, which fails with
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH because the lockfile still carries
the override that was just removed.

Pass `--no-frozen-lockfile` through to pnpm in the two affected snap
tests and note the requirement in the RFC's supported-versions list.

Also adds pnpm@11.x entries to the Test Package Manager Versions
sections of 7 RFCs covering add/remove/install/update/outdated/why/
dedupe/link-unlink.

Author: fengmk2

packages/cli/snap-tests-global/command-link-pnpm11/snap.txt

@@ -85,8 +85,43 @@ importers:
         specifier: link:../test-lib-pnpm
         version: link:../test-lib-pnpm
 
-[1]> vp unlink ../test-lib-pnpm && vp unlink testnpm2 && cat package.json pnpm-lock.yaml # should unlink the package
+> vp unlink ../test-lib-pnpm -- --no-frozen-lockfile && vp unlink testnpm2 -- --no-frozen-lockfile && cat package.json pnpm-lock.yaml # should unlink the package (pnpm v11 requires --no-frozen-lockfile under CI=true to avoid ERR_PNPM_LOCKFILE_CONFIG_MISMATCH)
 Already up to date
- ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "overrides" configuration doesn't match the value found in the lockfile
+testnpm2 is linked to <cwd>/node_modules from <cwd>/../test-lib-pnpm
+Already up to date
+Progress: resolved <variable>, reused <variable>, downloaded <variable>, added <variable>, done
+
+dependencies:
+- testnpm2 <semver>
++ testnpm2 <semver>
+
+{
+  "name": "command-link-pnpm11",
+  "version": "1.0.0",
+  "dependencies": {
+    "testnpm2": "*"
+  },
+  "packageManager": "pnpm@<semver>
+}
+lockfileVersion: '9.0'
+
+settings:
+  autoInstallPeers: true
+  excludeLinksFromLockfile: false
+
+importers:
+
+  .:
+    dependencies:
+      testnpm2:
+        specifier: '*'
+        version: <semver>
+
+packages:
+
+  testnpm2@<semver>:
+    resolution: {integrity: sha512-<hash>
+
+snapshots:
 
-Update your lockfile using "pnpm install --no-frozen-lockfile"
+  testnpm2@<semver>: {}

packages/cli/snap-tests-global/command-link-pnpm11/steps.json

@@ -6,6 +6,6 @@
     "mkdir -p ../test-lib-pnpm && echo '{\"name\": \"testnpm2\", \"version\": \"1.0.0\"}' > ../test-lib-pnpm/package.json # create test library",
     "vp link ../test-lib-pnpm && cat package.json pnpm-lock.yaml # should link local directory",
     "vp ln ../test-lib-pnpm && cat package.json pnpm-lock.yaml # should work with ln alias",
-    "vp unlink ../test-lib-pnpm && vp unlink testnpm2 && cat package.json pnpm-lock.yaml # should unlink the package"
+    "vp unlink ../test-lib-pnpm -- --no-frozen-lockfile && vp unlink testnpm2 -- --no-frozen-lockfile && cat package.json pnpm-lock.yaml # should unlink the package (pnpm v11 requires --no-frozen-lockfile under CI=true to avoid ERR_PNPM_LOCKFILE_CONFIG_MISMATCH)"
   ]
 }

packages/cli/snap-tests-global/command-unlink-pnpm11/snap.txt

@@ -29,16 +29,29 @@ dependencies:
   }
 }
 
-[1]> vp unlink unlink-test-lib && cat package.json # should unlink the package
- ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "overrides" configuration doesn't match the value found in the lockfile
+> vp unlink unlink-test-lib -- --no-frozen-lockfile && cat package.json # should unlink the package (pnpm v11 requires --no-frozen-lockfile under CI=true)
+Already up to date
 
-Update your lockfile using "pnpm install --no-frozen-lockfile"
+{
+  "name": "command-unlink-pnpm11",
+  "version": "1.0.0",
+  "packageManager": "pnpm@<semver>
+  "dependencies": {
+    "unlink-test-lib": "link:../unlink-test-lib"
+  }
+}
 
 > vp link ../unlink-test-lib # link again
-Lockfile is up to date, resolution step is skipped
 
 
-[1]> vp unlink && cat package.json # should unlink all packages
- ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "overrides" configuration doesn't match the value found in the lockfile
+> vp unlink -- --no-frozen-lockfile && cat package.json # should unlink all packages
+Already up to date
 
-Update your lockfile using "pnpm install --no-frozen-lockfile"
+{
+  "name": "command-unlink-pnpm11",
+  "version": "1.0.0",
+  "packageManager": "pnpm@<semver>
+  "dependencies": {
+    "unlink-test-lib": "link:../unlink-test-lib"
+  }
+}

packages/cli/snap-tests-global/command-unlink-pnpm11/steps.json

@@ -4,8 +4,8 @@
     "vp unlink -h # should show help message",
     "mkdir -p ../unlink-test-lib && echo '{\"name\": \"unlink-test-lib\", \"version\": \"1.0.0\"}' > ../unlink-test-lib/package.json # create test library",
     "vp link ../unlink-test-lib && cat package.json # link the library first",
-    "vp unlink unlink-test-lib && cat package.json # should unlink the package",
+    "vp unlink unlink-test-lib -- --no-frozen-lockfile && cat package.json # should unlink the package (pnpm v11 requires --no-frozen-lockfile under CI=true)",
     "vp link ../unlink-test-lib # link again",
-    "vp unlink && cat package.json # should unlink all packages"
+    "vp unlink -- --no-frozen-lockfile && cat package.json # should unlink all packages"
   ]
 }

rfcs/link-unlink-package-commands.md

@@ -753,7 +753,7 @@ $ vp link
 
 - pnpm@9.x
 - pnpm@10.x
-- pnpm@11.x [WIP] (unlink currently blocked by `ERR_PNPM_LOCKFILE_CONFIG_MISMATCH`)
+- pnpm@11.x [WIP] (pass `-- --no-frozen-lockfile` to `vp unlink` under CI=true; see snap-tests `command-unlink-pnpm11`)
 - yarn@1.x
 - yarn@4.x
 - npm@10.x