chore(deps): bump ignore from 5.3.2 to 7.0.6

[dependabot]

Bumps ignore from 5.3.2 to 7.0.6.

Release notes

Sourced from ignore's releases.

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:${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.

6.x (== 5.3.2)

... (truncated)

Commits

• 3823b5f 7.0.6
• f7520e2 test: adds tests for #153
• 424a2bb Merge pull request #161 from spokodev/fix/consecutive-leading-globstar
• e5cbe4a fix: consecutive leading **/ should match like a single **/
• ac68603 Merge pull request #159 from spokodev/fix/negated-character-class
• 5ba6b40 fix: negated character class [!...] should match like git
• 84d052d 7.0.5: fixes #152
• 1c6d762 #152: test: try to fix coverage
• a384835 #152: remove process.env access from the package
• 6c57760 README.md: typo
• Additional commits viewable in compare view

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)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[qmarcelle]

Closing in favour of #7.

ignore is declared in dependencies but never imported — zero references of any kind in packages/rules/src. This PR's green CI reflects that nothing exercises the package, not that 5.3.2 → 7.0.6 is safe.

#7 removes it outright, along with dedent, unified and zod, and adds an unused-dependency guard so a declared-but-unimported runtime dependency fails the build.

[dependabot]

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. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

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