Skip to content
This repository has been archived by the owner on Jun 13, 2023. It is now read-only.

[js] Update eslint: 7.17.0 → 7.18.0 (minor) #177

Merged
merged 1 commit into from
Jan 18, 2021

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jan 17, 2021

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 (7.17.0 → 7.18.0) · Repo · Changelog

Release Notes

7.18.0

  • e3264b2 Upgrade: @eslint/eslintrc to improve error message for invalid extends (#14009) (Milos Djermanovic)
  • f17c3c3 Update: check logical assignment operators in the complexity rule (#13979) (Milos Djermanovic)
  • 672deb0 Docs: fix no-invalid-regexp docs regarding ecmaVersion (#13991) (Milos Djermanovic)
  • 179a910 Fix: --init crash on question to upgrade/downgrade ESLint (fixes #13978) (#13995) (Milos Djermanovic)
  • 292b1c0 Fix: no-extra-parens false positive with let identifier in for-loop (#13981) (Milos Djermanovic)
  • de61f94 Sponsors: Sync README with website (ESLint Jenkins)
  • 9250d16 Upgrade: Bump lodash to fix security issue (#13993) (Frederik Prijck)
  • 75fea9b Sponsors: Sync README with website (ESLint Jenkins)
  • f2687e7 Docs: update space-in-parens related rules (#13985) (Chris Brody)
  • 4a38bbe Docs: space-in-parens examples with no arguments etc. (#13987) (Chris Brody)
  • 3e49169 Sponsors: Sync README with website (ESLint Jenkins)
  • c5bf1f2 Sponsors: Sync README with website (ESLint Jenkins)
  • 98a729c Sponsors: Sync README with website (ESLint Jenkins)
  • e83a696 Sponsors: Sync README with website (ESLint Jenkins)
  • 78cb483 Chore: test foo( ) with space-in-parens option "always" (#13986) (Chris Brody)
  • f6948f6 Docs: Update semantic versioning policy (#13970) (Nicholas C. Zakas)
  • 0688212 Sponsors: Sync README with website (ESLint Jenkins)
  • aeba5e5 Chore: fix typo (#13975) (Nitin Kumar)
  • 4ee1134 Sponsors: Sync README with website (ESLint Jenkins)

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

Commits

See the full diff on Github. The new version differs by 21 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)

@depfu depfu bot added the depfu label Jan 17, 2021
@codecov
Copy link

codecov bot commented Jan 17, 2021

Codecov Report

Merging #177 (609e032) into main (2272532) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #177   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines           34        34           
=========================================
  Hits            34        34           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2272532...609e032. Read the comment docs.

@ruebot ruebot merged commit 6cc8612 into main Jan 18, 2021
@depfu depfu bot deleted the depfu/update/npm/eslint-7.18.0 branch January 18, 2021 01:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant