Skip to content

Update ignore 5.2.4 → 7.0.5 (major)#266

Open
depfu[bot] wants to merge 1 commit into
masterfrom
depfu/update/yarn/ignore-7.0.5
Open

Update ignore 5.2.4 → 7.0.5 (major)#266
depfu[bot] wants to merge 1 commit into
masterfrom
depfu/update/yarn/ignore-7.0.5

Conversation

@depfu

@depfu depfu Bot commented Jun 1, 2025

Copy link
Copy Markdown
Contributor

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ ignore (5.2.4 → 7.0.5) · Repo · Changelog

Release Notes

7.0.4

  • 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

7.0.0

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:<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">result</span><span class="pl-kos">}</span></span>:<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">rule</span><span class="pl-kos">.</span><span class="pl-c1">mark</span><span class="pl-kos">}</span></span>:<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">rule</span><span class="pl-kos">.</span><span class="pl-c1">pattern</span><span class="pl-kos">}</span></span> 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.

5.3.0

5.3.0

  • MINOR export Options interface (#105)

An upgrade is safe for all dependents

It allows typing external methods which expect Options as a param, by importing the Options interface.

import {Options} from 'ignore'

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 75 commits:

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added the depfu label Jun 1, 2025
@depfu depfu Bot mentioned this pull request Jun 1, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants