Hugh Hackman
ca5ab75f6b
pnpm/action-setup@v4 errors with ERR_PNPM_BAD_PM_VERSION when both `version` (in the workflow) and `packageManager` (in package.json) are specified. Remove the hardcoded `version: latest` from plugin-release so that repos can pin their pnpm version via the packageManager field in package.json. When packageManager is absent the action falls back to latest (same prior behavior). When packageManager is set it is used exclusively, which prevents silent version drift. The plugin-ci.yaml change is handled separately in PR #54. Co-Authored-By: Paperclip <noreply@paperclip.ing>