Fix ineffective picomatch security override - #132
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The earlier selector-style override did not rewrite the lockfile:
picomatchremained at vulnerable 2.3.1. This changes the override to a package-wide 2.3.2 pin, regenerates the lockfile with Node 20.15.0/npm 10, and preserves Tailwind 3 rather than introducing an unrelated Tailwind 4 migration.The temporary lockfile generator will be removed before merge. The final branch must pass deterministic install, lint, component tests, production build, and Cypress E2E.