Update eslint → 8.56.0 (unknown) #55
Closed
Conversation
This file contains 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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
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?
✳️ eslint (^0.19.0 → ^8.56.0) · Repo · Changelog
Release Notes
8.56.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
8.56.0Build: changelog update for 8.56.0chore: upgrade @eslint/js@8.56.0 (#17864)chore: package.json update for @eslint/js releasefeat: Support custom severity when reporting unused disable directives (#17212)feat: fix no-restricted-properties false negatives with unknown objects (#17818)chore: update dependency markdownlint to ^0.32.0 (#17783)fix: `TypeError: fs.exists is not a function` on read-only file system (#17846)chore: add GitHub issue template for docs issues (#17845)chore: Convert rule tests to FlatRuleTester (#17819)docs: update link in ways-to-extend.md (#17839)chore: upgrade eslint-plugin-unicorn to v49.0.0 (#17837)chore: upgrade eslint-plugin-eslint-plugin v5.2.1 (#17838)chore: update eslint-plugin-n v16.4.0 (#17836)docs: Update READMEdocs: fix migration-guide example (#17829)docs: check config comments in rule examples (#17815)docs: remove mention about ESLint stylistic rules in readme (#17810)ci: unpin Node.js 21.2.0 (#17821)docs: Update READMEfix: suggestion with invalid syntax in no-promise-executor-return rule (#17812)👉 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