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-yaml: ^4.1.1andlodash-es: ^4.17.21, so it no longer matches this manifest. The PR checks in.github/workflows/pr-checks.ymluse.github/actions/setup-pnpm/action.yml, whose dependency-install step runspnpm installwithout overriding frozen-lockfile behavior. The pnpm documentation states that this setting is enabled by default in CI and installation “fails to install if the lockfile is out of sync with the manifest”. Consequently, these checks and the other workflows sharing that action stop at dependency installation. Regenerate and commit the lockfile with both upgrades.Useful? React with 👍 / 👎.