build(deps): bump picomatch from 2.3.1 to 2.3.2

[dependabot]

Bumps picomatch from 2.3.1 to 2.3.2.

Release notes

Sourced from picomatch's releases.

2.3.2

This is a security release fixing several security relevant issues.

What's Changed

• fix: exception when glob pattern contains constructor by @​Jason3S in micromatch/picomatch#144
• Fix for CVE-2026-33671
• Fix for CVE-2026-33672

Full Changelog: micromatch/picomatch@2.3.1...2.3.2

Changelog

Sourced from picomatch's changelog.

Release history

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

• Changelogs are for humans, not machines.
• There should be an entry for every single version.
• The same types of changes should be grouped.
• Versions and sections should be linkable.
• The latest version comes first.
• The release date of each versions is displayed.
• Mention whether you follow Semantic Versioning.

Changelog entries are classified using the following labels (from keep-a-changelog):

• Added for new features.
• Changed for changes in existing functionality.
• Deprecated for soon-to-be removed features.
• Removed for now removed features.
• Fixed for any bug fixes.
• Security in case of vulnerabilities.

4.0.0 (2024-02-07)

Fixes

• Fix bad text values in parse #126, thanks to @​connor4312

Changed

• Remove process global to work outside of node #129, thanks to @​styfle
• Add sideEffects to package.json #128, thanks to @​frandiox
• Removed os, make compatible browser environment. See #124, thanks to @​gwsbhqt

3.0.1

Fixes

... (truncated)

Commits

• 81cba8d Publish 2.3.2
• fc1f6b6 Merge commit from fork
• eec17ae Merge commit from fork
• 78f8ca4 Merge pull request #156 from micromatch/backport-144
• 3f4f10e Merge pull request #144 from Jason3S/jdent-object-properties
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[bri-tong]

Code Review — PR #9: bump picomatch from 2.3.1 to 2.3.2

Summary

This is an automated Dependabot security patch that bumps picomatch from 2.3.1 to 2.3.2 in yarn.lock. The update addresses two CVEs (CVE-2026-33671 and CVE-2026-33672) and a constructor-related exception fix. The change is limited to 3 lines in the lockfile (version, resolution, and checksum) with no application code changes.

Blocking Issues

None. This is a clean, minimal lockfile-only patch version bump for a security fix.

Non-blocking Suggestions

1. Verify package.json version range compatibility: The existing semver ranges (^2.0.4, ^2.2.3, ^2.3.1) all satisfy 2.3.2, so the resolution is correct. No action needed — just noting the verification was done.

2. Consider running the test suite before merging: The mergeable_state is currently blocked (likely due to branch protection rules or required status checks). Ensure CI passes green before merging. Since picomatch is a transitive dependency used by @rollup/pluginutils, anymatch, and jest-haste-map, a full test run would confirm no regressions in glob matching behavior.

3. package.json not updated: Note that picomatch is not a direct dependency — it's only a transitive dep. The package.json correctly does not change, and the lockfile update is the right approach here.

Questions / Clarifications

None — this is a straightforward, well-scoped security patch from Dependabot.

---

Verdict: ✅ Safe to merge once CI checks pass. The patch version bump (2.3.1 → 2.3.2) is semver-compatible, lockfile-only, and addresses known security vulnerabilities.