Skip to content

Bump picomatch from 2.3.1 to 2.3.2#2188

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/picomatch-2.3.2
Closed

Bump picomatch from 2.3.1 to 2.3.2#2188
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/picomatch-2.3.2

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Mar 27, 2026

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

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

Changed

3.0.1

Fixes

... (truncated)

Commits

Dependabot compatibility score

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.

Bumps [picomatch](https://github.com/micromatch/picomatch) from 2.3.1 to 2.3.2.
- [Release notes](https://github.com/micromatch/picomatch/releases)
- [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/picomatch@2.3.1...2.3.2)

---
updated-dependencies:
- dependency-name: picomatch
  dependency-version: 2.3.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Mar 27, 2026
@HeikoTheissen
Copy link
Copy Markdown
Contributor

HeikoTheissen commented Mar 27, 2026

The mocha package keeps introducing vulnerabilities, which npm audit fix tries to resolve by installing ever-older versions of it. Can we replace this package altogether?

Possibly related to oasis-tcs/odata-openapi#349

@HeikoTheissen HeikoTheissen moved this to Ready to discuss in OData TC Mar 27, 2026
@mikepizzo
Copy link
Copy Markdown
Contributor

Christof will look to see if there is a way to address vulnerabilities in, or remove the dependency on, the mocha unit test framework.

Question: what is our vulnerability to this package, given that it is in our repo, not our distributables?

@mikepizzo mikepizzo moved this from Ready to discuss to Open in OData TC Apr 1, 2026
@chrisspre
Copy link
Copy Markdown

chrisspre commented Apr 1, 2026

https://mochajs.org/explainers/security-vulnerability-reports/

Mocha explicitly addresses this class of reports in their Security Vulnerability Reports page.
Key points Mocha maintainers make:

Mocha is a dev‑time test framework, not production middleware
It does not process untrusted user input in normal usage
Most transitive vulnerabilities do not apply in practice
They track such issues transparently but do not consider many actionable

This is documented directly by Mocha themselves, including guidance for compliance‑driven environments.

picomatch-issu.md

@chrisspre chrisspre moved this from Open to Ready to discuss in OData TC Apr 8, 2026
@chrisspre
Copy link
Copy Markdown

PR for this: #2196

@github-project-automation github-project-automation Bot moved this from Ready to discuss to Review in OData TC Apr 8, 2026
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Apr 27, 2026

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@github-project-automation github-project-automation Bot moved this from Review to Closed in OData TC Apr 27, 2026
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/picomatch-2.3.2 branch April 27, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code V4.02

Projects

Status: Closed

Development

Successfully merging this pull request may close these issues.

4 participants