An in-range update of tslint is breaking the build 🚨
Closed this issue · 1 comments
Version 5.5.0 of tslint just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | tslint |
Current Version | 5.4.3 |
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 💪
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
v5.5.0Editor's note: This release features an important bugfix for overlapping fixes when using --project
and --fix
(#2864).
🎉 New rules and options
- [new-rule-option]
completed-docs
: Addenum-members
option (#2911) - [new-rule]
no-this-reassignment
(#2931)
🛠 Bugfixes & enhancements
- [bugfix]
encoding
closes files correctly (#2958) - [bugfix]
whitespace
fix whitespace"check-module"
to properly lint and fix errors (#2401) (#2825) - [bugfix]:
whitespace
: now correctly handles dynamic imports introduced in typescript@2.4.0 (#2924) - [bugfix]
switch-final-break
: don't fail if break jumps to a label outside of the switch (#2914) - [bugfix]
no-shadowed-variable
: exemptthis
parameter (#2598) - [bugfix]
prefer-for-of
correctly handles variable scopes and other unrelated identifiers (#2984) - [bugfix] Don't leave blank lines when
no-unused-variable
autofix removes whole import (#2901) - [cli] restore
-v
option (#2926) - [enhancement] Print stack trace of exceptions (#2890)
- [enhancement] Added allow-empty-catch option to
no-empty
(#2886) - [enhancement]
prefer-const
: handle destructuring in for-of loop initializer as if{"destructuring": "all"}
was specified (#2904) - [enhancement]
no-shadowed-variable
: added checks for other shadowing declarations, e.g. interfaces, classes, type parameters, imports, etc. (#2598) - [rule-change]
no-shadowed-variable
no longer fails for declarations in the same scope, e.g.var foo; var foo;
. Use the ruleno-duplicate-variable
to find such errors. (#2598)
Thanks to our contributors!
- Klaus Meinhardt
- Josh Goldberg
- Petr Kosikhin
- Pablo Núñez
- Benny Neugebauer
- Radon Rosborough
- reduckted
- Chris Barr
- Julian Verdurmen
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
After pinning to 5.4.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.