Update eslint 8.39.0 → 8.42.0 (minor) #34
Closed
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint (8.39.0 → 8.42.0) · Repo · Changelog
Release Notes
8.42.0
8.41.0
8.40.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 52 commits:
8.42.0Build: changelog update for 8.42.0chore: upgrade @eslint/js@8.42.0 (#17236)chore: package.json update for @eslint/js releaserefactor: remove `Identifier` listener in no-irregular-whitespace (#17235)fix: Config with `ignores` and without `files` should not always apply (#17181)docs: Update READMEtest: Add `FlatESLint` tests with missing config files (#17164)docs: Update READMEfix: Correct ignore message for "node_modules" subfolders (#17217)chore: Fix `fixedsize` attribute in code path analysis DOT debug output (#17202)feat: correct no-useless-return behaviour in try statements (#16996)chore: update descriptions in key-spacing tests (#17195)8.41.0Build: changelog update for 8.41.0chore: upgrade @eslint/js@8.41.0 (#17200)chore: package.json update for @eslint/js releasefix: incorrect warning message for ignored dotfiles (#17196)chore: don't use deprecated `context` methods in `ast-utils` tests (#17194)feat: change default ignore pattern to `**/node_modules/` in flat config (#17184)fix: unify `LintMessage` type (#17076)docs: Update READMEfeat: expose `shouldUseFlatConfig` (#17169)docs: Update triage process description (#17157)fix: validate `ignorePatterns` constructor option in `FlatESLint` class (#17139)chore: Fix return type of `findFlatConfigFile` (#17161)docs: fix license to reflect relicensing of jshint (#17165)fix: switch `grapheme-splitter` to `graphemer` (#17160)perf: Store indent descriptors in a plain array (#17148)refactor: locateConfigFileToUse returns an Error object (#17159)8.40.0Build: changelog update for 8.40.0chore: upgrade @eslint/js@8.40.0 (#17156)chore: package.json update for @eslint/js releasefix: Ensure FlatESLint#findConfigFile() doesn't throw. (#17151)chore: upgrade @eslint/eslintrc@2.0.3 (#17155)chore: upgrade espree@9.5.2 (#17154)chore: upgrade eslint-visitor-keys@3.4.1 (#17153)feat: improve flat config errors for invalid rule options and severities (#17140)feat: Add findConfigFile() method to FlatESLint (#17142)feat: add `sourceCode` property to the rule context (#17107)docs: Update READMEchore: add `latest/` to `meta.docs.url` in all core rules (#17136)feat: add `physicalFilename` property to the rule context (#17111)feat: add `cwd` to rule context (#17106)feat: add `filename` property to the rule context (#17108)feat: add new `omitLastInOneLineClassBody` option to the `semi` rule (#17105)docs: Update READMEperf: don't use `grapheme-splitter` on ASCII strings in key-spacing rule (#17122)docs: Fix custom rule schema docs (#17115)docs: explain how to include predefined globals (#17114)docs: add mastodon link in readme (#17110)👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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