* fix(config): read workspaces that use pnpm 12 task settings
`pnpm-workspace.yaml` is one format across pnpm 11 and 12, but the `tasks`
reader treated its two fields as an exhaustive allowlist and threw on
anything else. pnpm 12 defines six more (`concurrencyGroup`, `outputs`,
`inputs`, `env`, `cache`, `cargoTargetDir`), so every pnpm 11 command in a
workspace that declares one failed before it started.
Check only the fields this version reads and leave the rest alone, matching
how unrecognized top-level settings are already handled. pnpm 12 keeps
rejecting an unknown task field, since it is the version that reads them all.
Also name `cargo`, `concurrencyGroups` and `pipelines` in the
other-version table so the top-level warning stops offering a pnpm 11
setting as a spelling correction.
This repository's own `pnpm-workspace.yaml` started using `concurrencyGroup`
in pnpm/pnpm#15071, which broke `node pd.js --version` in TS CI.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs(changeset): drop the instead-of tail from the release note
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(config): report a task setting that misspells one pnpm 11 reads
Ignoring every unrecognized task field also ignored a misspelled one, and a
misspelled `dependsOn` is not inert: the entry still exists, so the task takes
the empty dependency list an entry without `dependsOn` declares and runs
before what it meant to wait for.
Reject a field that differs from `concurrency` or `dependsOn` only in case.
No pnpm version declares two settings that close, so such a field is a typo,
and the check needs no list of the settings other versions read.
Cover the pnpm 12 entries of the other-version table, which reach users as
warning text and had no test.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
