An in-range update of @angular-devkit/core is breaking the build 🚨
greenkeeper opened this issue · comments
The dependency @angular-devkit/core was updated from 7.2.1
to 7.2.2
.
This version is covered by your current version range and after updating it in your project the build failed.
@angular-devkit/core 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
- ❌ Travis CI - Branch:
The build failed.
Release Notes for v7.2.2
Commits
@schematics/angular (7.2.2) | ||
Commit | Description | Notes |
|
assert no error logs in e2e | |
|
fix syntax error in main.ts after generating universal |
[Closes #13392] |
|
remove properties which are set by default from required |
[Closes #13010] |
@angular-devkit/build-angular (0.12.2) | ||
Commit | Description | Notes |
|
script chunk in angular.json return false then calling isInitial | |
|
`vendorSourceMap` not being recognized when passed directly |
[Closes #13414] |
|
only show production warning when having either styles on scripts optimization turn on |
[Closes #13415] |
|
add missing declaration types in build_angular schemas. |
[Closes #13388] |
|
prints a warning on --host on serve |
[Closes #11060] |
@angular-devkit/build-optimizer (0.12.2) | ||
Commit | Description | Notes |
|
support windows paths in rollup plugin | |
@angular-devkit/core (7.2.2) | ||
Commit | Description | Notes |
|
Make default and info log messages use default colors |
[Closes #13439] |
@ngtools/webpack (7.2.2) | ||
Commit | Description | Notes |
|
drop only unused default import when used with named imports | |
@schematics/update (0.12.2) | ||
Commit | Description | Notes |
|
ensure option is string when replacing environment variable references |
Special Thanks
Alan, Alan Agius, Keen Yee Liau, Renovate Bot, Johannes Steier, Mikel Ward, Matthias Gaudin, Hans Larsen, Filipe Silva, Moritz Benzenhöfer, 調月奏
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 🌴
After pinning to 7.2.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.