chore: 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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-10 14:20 UTC · Rule: default
• ❌ Checks failed · on draft merge queue: queuing master (a310a83) and #853 together #864
• 🚫 Left the queue — 2026-06-10 14:22 UTC · at a437acb0535c93619b77a1a0fea13bb54b0aa8a4

This pull request spent 1 minute 44 seconds in the queue, including 46 seconds running CI.

Waiting for

• status-success=Analyze (javascript)
• status-success=Semantic Pull Request

All conditions

• status-success=Analyze (javascript)
• status-success=Semantic Pull Request
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore: Bump picomatch from 2.3.1 to 2.3.2 #853
• status-success=Run Unit Tests

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Semantic Pull Request (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[s3cube]

@dependabot recreate

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-06-10 14:20 UTC · Rule: default · triggered by rule Automatically approve and merge Dependabot PRs
• ❌ Checks failed · on draft merge queue: queuing master (a310a83) and #853 together #864
• 🚫 Left the queue — 2026-06-10 14:22 UTC · at a437acb0535c93619b77a1a0fea13bb54b0aa8a4

This pull request spent 1 minute 44 seconds in the queue, including 46 seconds running CI.

Waiting for

• status-success=Analyze (javascript)
• status-success=Semantic Pull Request

All conditions

• status-success=Analyze (javascript)
• status-success=Semantic Pull Request
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore: Bump picomatch from 2.3.1 to 2.3.2 #853
• status-success=Run Unit Tests

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• 🟠 Analyze (javascript) (job log)
• ❌ Semantic Pull Request (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).

• Requeue this pull request