Skip to content
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-config-holy-grail is breaking the build 🚨 #66

Closed
greenkeeper bot opened this issue Jul 29, 2019 · 1 comment
Closed

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jul 29, 2019

The devDependency tslint-config-holy-grail was updated from 44.0.6 to 44.0.7.

🚨 View failing branch.

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

tslint-config-holy-grail 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

Commits

The new version differs by 12 commits.

  • 5535eb9 44.0.7
  • 45007ed fix(package): update zone.js to version 0.10.0
  • c1b665e fix(package): update mocha to version 6.2.0
  • 3741d26 fix(package): update load-grunt-config to version 2.0.1
  • 8a37c0f fix(package): update husky to version 3.0.1
  • 20ddae7 fix(package): update eslint-config-holy-grail to version 38.0.3
  • bfe90cf fix(package): update eslint to version 6.1.0
  • 6c5c539 fix(package): update cz-conventional-changelog to version 3.0.2
  • 74bf378 fix(package): update commitizen to version 4.0.3
  • 7218445 fix(package): update @angular/{compiler,core} to version 8.1.3
  • 3e11a52 fix(package): update @commitlint/config-angular to version 8.1.0
  • 3b9c5b2 fix(package): update @commitlint/cli to version 8.1.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 29, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant