chore: remove pnpm-lock.yaml with vulnerable deps#7591
Merged
Conversation
quirogas
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This lock file was likely accidentally committed by someone using pnpm locally. It is only covering our root package (not any of the underlying libraries in our monorepo).
Currently the underlying packages do not have their own lockfiles and this lock file will have no impact on our CI.
This may change in the future, but at the moment this is just creating noise.
Note: I have temporarily modified the CI so that all unit tests are rerun to bumping our repository versions will not cause breakages.