-
Notifications
You must be signed in to change notification settings - Fork 0
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
An in-range update of tslint is breaking the build 🚨 #6
Comments
Version 5.5.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.5.0Editor's note: This release features an important bugfix for overlapping fixes when using 🎉 New rules and options
🛠 Bugfixes & enhancements
Thanks to our contributors!
|
Version 5.6.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.6.0🎉 New rules, options, and fixers
🛠 Bugfixes & enhancements
Thanks to our contributors!
|
Version 5.7.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.7.0🎉 New rules, options, and fixers
🛠 Bugfixes & enhancements
Thanks to our contributors!
|
Version 5.8.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv5.8.0
|
Version 5.9.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.9.0
|
Version 5.9.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv5.9.1🛠 Bugfixes |
Version 5.4.3 of tslint just got published.
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
Release Notes
v5.4.3🛠 Bugfixes
--out
file (#2867)unified-signatures
: Don't suggest to unify rest parameters. (#2874)binary-expression-operand-order
: Allow if both sides of the binary expression are literals. (#2873)whitespace
,space-before-function-paren
anddeprecation
(#2893)no-string-literal
: Fix documentation (#2875)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 🌴
The text was updated successfully, but these errors were encountered: