This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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.
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 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)
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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.13.0 → 8.15.0) · Repo · Changelog
Release Notes
8.15.0
8.14.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 32 commits:
8.15.0
Build: changelog update for 8.15.0
chore: upgrade @eslint/eslintrc@1.2.3 (#15847)
fix: "use strict" should not trigger strict mode in ES3 (#15846)
docs: update AST node names link in no-restricted-syntax (#15843)
chore: bump version of minimatch due to security issue PRISMA-2022-0039 (#15774)
docs: fix h1 heading on formatters page (#15834)
docs: update example for running individual rule tests (#15833)
chore: Implement docs site (#15815)
feat: add `enforceInClassFields` option to no-underscore-dangle (#15818)
Sponsors: Sync README with website
docs: mark `SourceCode#getJSDocComment` deprecated in working-with-rules (#15829)
docs: update docs directory in working-with-rules (#15830)
docs: add more examples for prefer-object-spread (#15831)
Sponsors: Sync README with website
Sponsors: Sync README with website
docs: clarify no-control-regex rule (#15808)
chore: update link in `codeql-analysis.yml` (#15817)
docs: Fixed typo in code comment (#15812)
chore: enable no-constant-binary-expression in eslint-config-eslint (#15807)
docs: remove links to 2fa document (#15804)
docs: fix 'Related Rules' heading in no-constant-binary-expression (#15799)
docs: Update README team and sponsors
8.14.0
Build: changelog update for 8.14.0
fix: allow project paths to have URL-encoded characters (#15795)
chore: add static frontmatter to no-constant-binary-expression docs (#15798)
feat: Add rule no-constant-binary-expression (#15296)
chore: Add static frontmatter to docs (#15782)
build: add node v18 (#15791)
fix: update `astUtils.isDirectiveComment` with `globals` and `exported` (#15775)
chore: markdownlint autofix on commit (#15783)
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