micromatch
4.0.8 · 23 Aug 2024MIT222.4M / weekRepositorynpmAtom feed
Upgrading micromatch From 2.1.6 to 4.0.8
39 releases in betweennotes for 12
Reading releases, release notes and advisories…
Counted from 12 of 39 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
Security
Fixes 1 advisory affecting 2.1.6
- Regular Expression Denial of Service (ReDoS) in micromatchmoderate · GHSA-952p-6rrq-rcjv
- 4.0.8
Ultimate release that fixes both CVE-2024-4067 and CVE-2024-4068.
- 4.0.7
It is vulnerable to CVE-2024-4067
- 4.0.7
Updated braces to v3.0.3 to avoid CVE-2024-4068
- 4.0.6
Fixes CVE-2024-4067
Release by release
- Security
Ultimate release that fixes both CVE-2024-4067 and CVE-2024-4068.
- Security
- Security
It is vulnerable to CVE-2024-4067
- Security
Updated braces to v3.0.3 to avoid CVE-2024-4068
- Security
- Security
Fixes CVE-2024-4067
- New
Added
hasBracesto check if a pattern contains braces.
- Security
4.0.5no release note
- Fixed
Update picomatch to fix regression #179
- Fixed
4.0.1 – 4.0.33 releases, nothing new or fixed; 2 without a note
- Breaking
Require Node.js >= 8.6
- Breaking
Removed support for passing an array of brace patterns to
micromatch.braces(). - Breaking
To strictly enforce closing brackets (for
{,[, and(), you must now usestrictBrackets=trueinstead ofstrictErrors. - Breaking
cache- caching and all related options and methods have been removed
- Breaking
2.2.0 – 3.1.1030 releases, nothing new or fixed; 24 without a note
14 other lines we could not sort, mostly version bumps
- 4.0.7
This is basically v4.0.5, with some README updates
- 4.0.7
Does NOT break API compatibility
- 4.0.6
BREAKS API COMPATIBILITY
- 4.0.6
Should be labeled as a major release, but it's not.
- 4.0.3
Enforce newer version of picomatch with bugfixes
- 3.0.0
Micromatch results are directly compared to bash results
- 3.0.0
In rare cases, when micromatch and bash disagree, micromatch's results are compared to minimatch's results
- 3.0.0
Micromatch is much more accurate than minimatch, so there were cases where I had to make assumptions. I'll try to document these.
- 3.0.0
Source map support (optionally created when using parse or compile - I have no idea what the use case is yet, but they come for free) (note that source maps are not generated for brace expansion at present, since the braces compiler uses a different strategy. I'll update if/when this changes).
- 3.0.0
Parser is exposed, so that implementors can customize or override specific micromatch parsers if necessary
1 internal line (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.