Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These manifest changes leave
pnpm-lock.yamlwith the old specifiers (^4.1.1and^4.17.21). The install in.github/actions/setup-pnpm/action.yml:35, used by the PR workflows, runs in CI where pnpm documents that--frozen-lockfileis enabled by default; running it against this tree producesERR_PNPM_OUTDATED_LOCKFILEfor both dependencies, so every affected workflow fails during setup before validation can run. Commit the regenerated lockfile alongside these upgrades.Useful? React with 👍 / 👎.