This version is covered by your current version range and after updating it in your project the build failed.
restify is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
❌ ci/circleci Your tests failed on CircleCI Details
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
❌ ci/circleci Your tests failed on CircleCI Details
Release Notesv5.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
[feature] Support yaml configuration files (#1598) (#3433)
[new-rule-option] "temporalDeadZone" for no-shadowed-variable to ignore shadowing in the temporal dead zone of classes, parameters, enums and variables declared with let or const
(#3389)
This version is covered by your current version range and after updating it in your project the build failed.
nyc 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
source-map-support 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
typescript 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
@types/restify 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
botbuilder is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
@types/lodash 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
@types/chai 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
❌ ci/circleci Your tests failed on CircleCI Details
Version 10 of Node.js (code name Dubnium) has been released! 🎊
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
Replaced the old Node.js version in your .nvmrc with the new one
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone
If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
More information on this issue
Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.
engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.
For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖
This version is covered by your current version range and after updating it in your project the build failed.
restify is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
mocha 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
@types/mocha 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
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
@types/bunyan 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
❌ ci/circleci: Your tests failed on CircleCI (Details).
This version is covered by your current version range and after updating it in your project the build failed.
botbuilder is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
❌ ci/circleci Your tests failed on CircleCI Details
This version is covered by your current version range and after updating it in your project the build failed.
lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
❌ ci/circleci Your tests failed on CircleCI Details