Skip to content

An in-range update of @typescript-eslint/eslint-plugin is breaking the build 🚨 #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
greenkeeper bot opened this issue Oct 14, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 14, 2019

The devDependency @typescript-eslint/eslint-plugin was updated from 2.3.3 to 2.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

Release Notes for v2.4.0

2.4.0 (2019-10-14)

Bug Fixes

  • eslint-plugin: [promise-function-async] Should not report… (#1023) (514bed9)
  • support long running "watch" lint sessions (#973) (854620e)

Features

  • typescript-estree: support for parsing 3.7 features (#1045) (623febf)
Commits

The new version differs by 8 commits.

  • 111ecc6 chore: publish v2.4.0
  • 623febf feat(typescript-estree): support for parsing 3.7 features (#1045)
  • 854620e fix: support long running "watch" lint sessions (#973)
  • fec73b0 docs: clarify which versions of ESLint are supported (#1073)
  • 5f92b9f docs: add TOC to root README (#838)
  • 526d336 chore: add test for function types & no-restricted-globals rule (#1055)
  • 514bed9 fix(eslint-plugin): [promise-function-async] Should not report… (#1023)
  • a3f84e1 chore(eslint-plugin): Add missing rule function types (#1047)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 14, 2019

After pinning to 2.3.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant