Repository navigation
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.
The committed
pnpm-lock.yamlstill specifiesjs-yamlas^4.1.1/4.1.1andlodash-esas^4.17.21/4.17.23, so it is out of sync with these manifest changes. Every checked workflow installs through.github/actions/setup-pnpm/action.yml:35, and pnpm documents that CI enables frozen-lockfile behavior and fails when the lockfile and manifest differ; reproducing that install reportsERR_PNPM_OUTDATED_LOCKFILEfor both dependencies. Commit the regeneratedpnpm-lock.yamlso PR checks and deployment/indexing workflows can install dependencies and the security upgrades are actually locked.Useful? React with 👍 / 👎.