search

papandreou / seespee

Create a Content-Security-Policy for a website based on the statically detectable relations
BSD 3-Clause "New" or "Revised" License
75 stars 4 forks source link

Upgrade eslint to version 8.4.0 #88

Closed depfu[bot] closed 2 years ago

depfu[bot] commented 2 years ago

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 (^7.0.0 → ^8.4.0) · Repo · Changelog

Release Notes

8.4.0

Features

  • 5771663 feat: add allowReserved parser option (#15387) (Milos Djermanovic)
  • 32ac37a feat: Flat config support in Linter (refs #13481) (#15185) (Nicholas C. Zakas)
  • d041f34 feat: Treat Class/New Expressions as truthy in no-constant-condition (#15326) (Jordan Eldredge)
  • 8f44cf5 feat: report only lines that exceed the limit in max-lines-per-function (#15140) (Sneh Khatri)
  • 808ad35 feat: pass cwd to formatters (refs eslint/rfcs#57) (#13392) (Toru Nagashima)
  • f1b7499 feat: support async formatters (#15243) (MO)

Bug Fixes

  • 4940cc5 fix: mark --rulesdir option as deprecated in CLI docs (#15310) (Kevin Partington)

Documentation

  • 54deec5 docs: update integrations.md (#15380) (Vlad Sholokhov)
  • fa0423a docs: fix typo in PR template (#15365) (Nitin Kumar)
  • e233920 docs: enable a few more markdownlint rules and fix violations (#15368) (Bryan Mishkin)
  • 632176d docs: Dedent needlessly indented example in getter-return docs (#15363) (Jordan Eldredge)
  • 4497e88 docs: Update release notes blog post template (#15285) (Nicholas C. Zakas)

Chores

  • efede90 chore: upgrade @eslint/eslintrc@1.0.5 (#15389) (Milos Djermanovic)
  • 0b8c846 chore: fix update-readme to avoid multiple consecutive blank lines (#15375) (Milos Djermanovic)
  • 94b2a8b chore: Use default Chromium binary in M1 Mac tests (#15371) (Brandon Mills)
  • ba58d94 ci: use node v16 for Verify Files (#15364) (Nitin Kumar)
  • 1e32ee5 chore: add jsdoc type annotation to rules (#15291) (Bryan Mishkin)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 26 commits:

Depfu Status

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)
coveralls commented 2 years ago

Coverage Status

Coverage remained the same at 82.941% when pulling e6cc049731b4bfe6e6f84c3f0895839247d988c5 on depfu/update/npm/eslint-8.4.0 into 65cc7aa66e7e420d5130e342b06fd63465bc6220 on master.

depfu[bot] commented 2 years ago

Closed in favor of #89.