Update eslint: 5.7.0 → 5.8.0 (minor) #66
Merged
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.
We've updated a dependency and here is what you need to know:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ eslint (5.7.0 → 5.8.0) · Repo · Changelog
Release Notes
5.8.0
Commits
See the full diff on Github. The new version differs by 14 commits:
5.8.0Build: changelog update for 5.8.0Fix: deprecation warning in RuleTester using Node v11 (#11009)Docs: Update issue templates to ask for PRs (#11012)Chore: avoid using legacy report API in no-irregular-whitespace (#11013)Build: compile espree's deps to ES5 when generating site (fixes #11014) (#11015)Update: Create Linter.version API (fixes #9271) (#11010)Docs: Mention version for config glob patterns (fixes #8793)Build: run tests on Node 11 (#11008)Docs: add instructions for npm 2FA (refs #10631) (#10992)Upgrade: eslint-release@1.0.0 (refs #10631) (#10991)Fix: prefer-const when using destructuring assign (fixes #8308) (#10924)Chore: Add typescript-specific edge case tests to space-infix-ops (#10986)Chore: Using deconstruction assignment for shelljs (#10974)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