Skip to content

chore(deps): update dependency ignore to v7#1031

Merged
B4nan merged 2 commits intomasterfrom
renovate/ignore-7.x
Mar 4, 2026
Merged

chore(deps): update dependency ignore to v7#1031
B4nan merged 2 commits intomasterfrom
renovate/ignore-7.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 2, 2026

This PR contains the following updates:

Package Change Age Confidence
ignore ^5.3.2^7.0.0 age confidence

Release Notes

kaelzhang/node-ignore (ignore)

v7.0.5

Compare Source

v7.0.4

Compare Source

  • PATCH Allows files named .{3,}, such as ... for Linux / macOS (#​68)
ig.ignores('...')
ig.ignores('....')
// It will throw a RangeError in versions prior to 7.0.4, but it is ok if >= 7.0.4

An upgrade is recommended for all dependents

v7.0.3

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source

Minor feature

The primary feature introduced by 7.0.0 is the .checkIgnore() method, which is most equivalent to git check-ignore -v. And also it allows to pass {pattern, mark?} as the parameter of .add() so that we could imitate the mechanism of git check-ignore as:

ig.add({
  pattern: 'foo/*',
  mark: '60'
})

const {
  ignored,
  rule
} = checkIgnore('foo/')

if (ignored) {
  console.log(`.gitignore:${result}:${rule.mark}:${rule.pattern} foo/`)
}

// .gitignore:60:foo/* foo/

Potential Incompatibilities

The only situation that 7.0.0 might bring incompatibility is to .add() a < 7.0.0 instance into a >= 7.0.0 instance, which might occur when the current workspace has multiple node-ignore versions installed, please be careful.

const {anotherIgnoreInstance} = require('./ignore-6.0-instance')

// A 7.0.0 instance
ignore().add(anotherIgnoreInstance)

// It will break your code

Otherwise, in most cases, if you never do something above or there is only one version of node-ignore installed in the current workspace, it is quite safe to upgrade to 7.0.0.

v6.0.2

Compare Source

v6.0.1: 6.x (== 5.3.2)

Compare Source

6.x

  • The release of 6.x is due to a mistake.
  • 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.
    • Actually 6.0.2 is 5.3.2
  • The next major release will be 7.0.0

v6.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from vladfrangu as a code owner March 2, 2026 09:55
@vladfrangu vladfrangu requested a review from l2ysho March 2, 2026 17:57
@renovate renovate bot force-pushed the renovate/ignore-7.x branch from 8c67e8b to e1dcefa Compare March 3, 2026 14:22
@B4nan
Copy link
Member

B4nan commented Mar 3, 2026

Huh, why did we use such an outdated version? 🙃

@renovate renovate bot force-pushed the renovate/ignore-7.x branch from e1dcefa to a67b9ca Compare March 4, 2026 14:34
@B4nan
Copy link
Member

B4nan commented Mar 4, 2026

We should merge this before the release (unless there is actual work to be done here, I don't remember if the CI was green or not).

@B4nan
Copy link
Member

B4nan commented Mar 4, 2026

CI is green, so merging...

@B4nan B4nan merged commit fbbccb4 into master Mar 4, 2026
63 of 64 checks passed
@B4nan B4nan deleted the renovate/ignore-7.x branch March 4, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant