Repository navigation
Unblock Dependabot by pinning micromatch’s vulnerable picomatch subdependency - #76
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-authored-by: tomtau <2410580+tomtau@users.noreply.github.com>
micromatch’s vulnerable picomatch subdependency
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The manifest and lockfile changes are consistent, narrowly scoped, and remove all picomatch@2.3.1 references.
Review effort: Balanced
Findings: None
What changed in this PR
Pins the vulnerable transitive picomatch dependency used by Parcel’s watcher chain.
Changes:
- Adds a scoped pnpm override for
micromatch>picomatch. - Aligns lockfile resolution to
picomatch@2.3.2.
| File | Description |
|---|---|
package.json |
Declares the scoped dependency override. |
pnpm-lock.yaml |
Records the override and updated resolution. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Dependabot’s security update job could not remediate
picomatchbecause this repo’s Parcel watcher chain resolvedmicromatch@4.0.5to vulnerablepicomatch@2.3.1, while the first safe 2.x release is2.3.2. This change makes that transitive resolution explicit so Dependabot can produce a valid update.Dependency resolution
micromatch>picomatchto force2.3.2Lockfile alignment
pnpm-lock.yamlmicromatch@4.0.5snapshot to resolvepicomatch: 2.3.2picomatch@2.3.1lock entry with2.3.2Result
picomatchversion{ "pnpm": { "overrides": { "micromatch>picomatch": "2.3.2" } } }