chore: cleanup package-lock from removed workspaces #7025
Merged
Conversation
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
gribnoysup
added
the
no-title-validation
addaleax
approved these changes
Jun 16, 2025
Collaborator
Author
Anemy
approved these changes
Jun 16, 2025
Collaborator
Up to you! It's basically more of a question whether you want me to be able to provide reviews or not 😅 |
Collaborator
Author
|
Asking mostly because it is pretty spammy right now if you're in compass devs group, totally want you to be able to review here 🙇 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Was looking into why update eslint behaves weird and noticed we still have references to these package we removed from the monorepo some time ago still in the package-lock. This is not the reason for what's tripping the update script, just a small drive-by clean up (it was causing some warnings on install)