AutoScheduleJS / conflict-resolver

MIT License
1 stars 0 forks source link

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

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 5.9.0 of tslint was just published.

Branch Build failing 🚨
Dependency tslint
Current Version 5.8.0
Type devDependency

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

tslint 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 - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/AutoScheduleJS/conflict-resolver/builds/327522338?utm_source=github_status&utm_medium=notification)

Release Notes v5.9.0

⚠️ Deprecations

  • [deprecation] Several utility functions from src/language/utils.ts have been deprecated (#3476)
  • [deprecation] Linting non-existent files now outputs a warning. This will be an error in TSLint 6. (#3313)

Configuration inheritance changes

Significant changes have been made to configuration inheritance to address a long-standing UX issue around defualtSeverity: #2569.

defaultSeverity defined in a tslint.json file will now override the defaultSeverity value defined in any configurations you are extending.
This means that any rules specified in the base configurations can now take on a new defaultSeverity if you so choose. If you extend multiple
configuration files, the defaultSeverity defined in the last one wins.

In practice, this allows users to, for example, more easily use the built-in TSLint configurations (tslint:recommended, tslint:latest, tslint:all)
and treat all errors as warnings instead of errors.

For more details, see the relevant PRs:

  • Override defaultSeverity defined in extended configs (#3449)
  • Inherit defaultSeverity and apply it to preceding base configs (#3530)

πŸŽ‰ Features

πŸ›  Bugfixes & enhancements

Thanks to our contributors!

  • Klaus Meinhardt
  • Josh Goldberg
  • Chris Barr
  • Nathan Shively-Sanders
  • Jeremy Morton
  • Sergey Koshechkin
  • Daniel Kucal
  • Eric Smekens
  • Johannes Choo
  • Elena Vilchik
  • Eugene Timokhov
  • Carlo Bottiglieri
  • reduckted
  • Glavin Wiechert
  • jbsingh
  • Mateusz Witkowski
  • HideDev
  • Bruno Lemos
  • aervin_
  • Roman
  • Ryan Waskiewicz
FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

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

greenkeeper[bot] commented 6 years ago

Version 5.9.1 just got published.

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

Release Notes v5.9.1

πŸ›  Bugfixes

  • [bugfix] Removed extraneous deprecation warning produced when using tslint:recommended or tslint:latest by disabling typeof-compare in these rulesets. (#3639)
  • [bugfix] Resolve directories as absolute paths when validating custom rulesDirectory paths, which fixes usage with tslint-loader. (#3640)