search

vladimir-barsuchenko / angular-tuned

2 stars 0 forks source link

An in-range update of webpack-cli is breaking the build 🚨 #59

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 6 years ago

Version 2.1.4 of webpack-cli was just published.

Branch Build failing 🚨
Dependency webpack-cli
Current Version 2.1.3
Type devDependency

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

webpack-cli 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](https://circleci.com/gh/levgaas/angular-tuned/174?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/levgaas/angular-tuned/builds/382761406?utm_source=github_status&utm_medium=notification)
Release Notes v2.1.4

2.1.4 (2018-05-23)

Bug Fixes

Commits

The new version differs by 10 commits.

  • 3953648 fix(dependencies): fix vulnerabilities (#458)
  • 7c01f39 chore(travis): move npm ci to install task (#424)
  • aefa520 chore(travis): add Node.js 10 (#425)
  • 8283ba9 chore(docs): update readme
  • 9760a4d Update dependencies to enable Greenkeeper 🌴 (#443)
  • 4cca655 chore(travis): run lockfile cmds on tests (#444)
  • d0fb42c cli(init): revise installation steps (#441)
  • 51851e8 fix(pkg): test auto setup
  • bb181a1 chore(travis): Add encrypted private ssh key
  • 2091d1c chore(package.lock): update pkg.lock

See the full diff

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 2.1.3 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 2.1.5 just got published.

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

Release Notes v2.1.5

2.1.5 (2018-06-01)

Bug Fixes

  • entry: fix a bug when --display-entrypoints=false does not hide entries (#464) (c2398a2)
Commits

The new version differs by 4 commits.

  • 3a8fcce chore(deps): Update conventional-changelog-cli to the latest version 🚀 (#474)
  • 3442865 tests(binTestCases): refactor to make tests pass (#472)
  • c2398a2 fix(entry): fix a bug when --display-entrypoints=false does not hide entries (#464)
  • 9977406 chore(package): update jest-cli to version 23.0.1 (#467)

See the full diff