search

unional / reactor-webpack-ts-plugin

Webpack TypeScript plugin for extjs-reactor
MIT License
0 stars 3 forks source link

An in-range update of tslint is breaking the build 🚨 #2

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 4.1.0 of tslint just got published.

Branch Build failing 🚨
Dependency tslint
Current Version 4.0.2
Type devDependency

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

As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/unional/reactor-webpack-ts-plugin/builds/184367391)
Release Notes v4.1.0
  • [new-rule] prefer-const (#1801)
  • [new-rule] strict-boolean-expressions (#1820)
  • [new-rule] no-magic-numbers (#1799)
  • [new-rule] import-blacklist (#1841)
  • [new-rule] promise-functions-async (#1779)
  • [new-rule] no-inferred-empty-object-type: a type must be specified when using a generic class/function/etc (#1821)
  • [new-rule-option] allow-named-functions added to only-arrow-functions (#1857)
  • [new-fixer] prefer-const (#1801)
  • [new-fixer] quotemark (#1790)
  • [new-formatter] code-frame formatter shows you the error in context (#1819)
  • [enhancement] no-internal-module failures highlight less text (#1781)
  • [enhancement] Avoid auto-fixing errors that would result in compilation errors for rules that use type-check (#1608)
  • [rule-change] only-arrow-functions will allow functions with a this parameter (#1597)
  • [bugfix] no-use-before-declare false positive on named import (#1620)
  • [bugfix] prefer-for-of was showing false positive when the element is assigned (#1813)
  • [bugfix] The command line argument type-check was swallowing the next argument (#1783)
  • [bugfix] tslint:disable-line was re-enabling tslint:disable (#1634)
  • [bugfix] adjacent-overload-signatures did not work for constructors (#1800)
  • [bugfix] checkstyle formatter was reporting errors under one file (#1811)
  • [bugfix] trailing-comma was applied to parameter lists (#1775)
  • [api] CLI logic moved into API friendly class (#1688)
Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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

greenkeeper[bot] commented 7 years ago

Version 4.1.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v4.1.1
  • [bugfix] typedef rule was showing false positive for catch clause (#1887)