Packages

ignore

7.0.16 · 17 Nov 2026MIT456.9M / weekRepositoryHomepagenpmAtom feed

Upgrading ignore From 6.0.0 to 7.0.16

18 releases in betweennotes for 4

Other targets from 6.0.0Newest 6.x6.0.2
The note of 7.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 6.0.0yours
  2. 2 releases
  3. 7.0.0major
  4. 14 releases
  5. 7.0.16target
?
changes to make
0
advisories fixed
1+
new
?
fixes

Counted from 4 of 18 release notes. Advisories are counted from the advisory database, in full.

Release by release

  1. 7.0.5 – 7.0.1611 releases, nothing new or fixed; 10 without a note

  2. 7.0.4

    25 Apr 20251 new
    • New

      PATCH Allows files named .{3,}, such as ... for Linux / macOS

  3. 6.0.1 – 7.0.36 releases, nothing new or fixed; 4 without a note

5 other lines we could not sort, mostly version bumps
  • PATCH A backslash now makes the next character a literal, exactly as git does: \* matches a literal * rather than acting as a wildcard, \? matches a literal ?, and \d, \b, \/ and the like are the plain characters instead of regular-expression escapes.

    7.0.8
  • PATCH Only a trailing run of spaces is stripped from a pattern — never tabs or other whitespace — and a line of only tabs is treated as a pattern rather than a blank line, matching git.

    7.0.8
  • The release of 6.x is due to a mistake.

    6.0.1
  • Making an upgrade from 5.x to 6.x for now actually changes nothing and does no harm, everyone could just upgrade or ignore the version.

    6.0.1
  • The next major release will be 7.0.0

    6.0.1

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.