-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[8.18] Update dependency ignore to v7 (main) (#203286) #222708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [ignore](https://github.com/kaelzhang/node-ignore) | devDependencies | major | [`^5.3.0` -> `^7.0.4`](https://renovatebot.com/diffs/npm/ignore/5.3.2/7.0.4) | `7.0.5` | --- ### Release Notes <details> <summary>kaelzhang/node-ignore (ignore)</summary> ### [`v7.0.4`](https://github.com/kaelzhang/node-ignore/releases/tag/7.0.4) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/7.0.3...7.0.4) - **PATCH** Allows files named `.{3,}`, such as `...` for Linux / macOS ([#&elastic#8203;68](https://github.com/kaelzhang/node-ignore/issues/68)) ```js 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`](https://github.com/kaelzhang/node-ignore/compare/52f8e855b6aca711579c008f38829f48e5a4c78b...7.0.3) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/52f8e855b6aca711579c008f38829f48e5a4c78b...7.0.3) ### [`v7.0.2`](https://github.com/kaelzhang/node-ignore/compare/7.0.1...52f8e855b6aca711579c008f38829f48e5a4c78b) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/7.0.1...52f8e855b6aca711579c008f38829f48e5a4c78b) ### [`v7.0.1`](https://github.com/kaelzhang/node-ignore/compare/7.0.0...7.0.1) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/7.0.0...7.0.1) ### [`v7.0.0`](https://github.com/kaelzhang/node-ignore/releases/tag/7.0.0) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/ee70c66d32e900f6e793c733a4ca27a1dafb3819...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: ```js 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. ```js 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`](https://github.com/kaelzhang/node-ignore/compare/6.0.1...ee70c66d32e900f6e793c733a4ca27a1dafb3819) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/6.0.1...ee70c66d32e900f6e793c733a4ca27a1dafb3819) ### [`v6.0.1`](https://github.com/kaelzhang/node-ignore/releases/tag/6.0.1): 6.x (== 5.3.2) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/6.0.0...6.0.1) ### 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`](https://github.com/kaelzhang/node-ignore/compare/5.3.2...6.0.0) [Compare Source](https://github.com/kaelzhang/node-ignore/compare/5.3.2...6.0.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDphbGwtb3BlbiIsInJlbGVhc2Vfbm90ZTpza2lwIl19--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: Brad White <[email protected]> (cherry picked from commit 2656cb4) # Conflicts: # yarn.lock
1 task
Contributor
💚 Build Succeeded
Metrics [docs]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto8.18:Questions ?
Please refer to the Backport tool documentation