On pnpm/setup@v2, CI actually pulls v2.0.2, not the latest v2.1.0
From log:
Download action repository 'pnpm/setup@v2' (SHA:84cb39b…)
On the tags page, v2 still points at the same commit as v2.0.2 (84cb39b), while v2.1.0 is 703c526 so publishing v2.1.0 didn't advance the v2 tag. Effect: @v2 users miss v2.1.0 and get Warning: Unexpected input(s) 'require-lockfile' because the input only exists in v2.1.0.
On
pnpm/setup@v2, CI actually pullsv2.0.2, not the latestv2.1.0From log:
Download action repository 'pnpm/setup@v2' (SHA:84cb39b…)On the tags page,
v2still points at the same commit as v2.0.2 (84cb39b), while v2.1.0 is 703c526 so publishingv2.1.0didn't advance thev2tag. Effect:@v2users missv2.1.0and getWarning: Unexpected input(s) 'require-lockfile'because the input only exists inv2.1.0.