An in-range update of config is breaking the build π¨
Closed this issue Β· 2 comments
The dependency config was updated from 3.2.2
to 3.2.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
config 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
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 π΄
- The
dependency
config was updated from3.2.3
to3.2.4
.
Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
- The
dependency
config was updated from3.2.6
to3.3.0
.
Your tests for group default are passing again with this update. Explicitly upgrade default to this version π
Commits
The new version differs by 13 commits.
080d9f9
Prepare for 3.3.0 publish
945aed3
Merge pull request #582 from fostyfost/master
c42e3fa
Allow all defined values in
substituteDeep
9fa7022
Updated copyright dates
d3616e6
Updated copyright dates
21d3094
Prepare for 3.2.5 publish
3268b40
Merge pull request #585 from dekelev/master
dbcddbb
Fixed issue with getCustomEnvVars method and multiple config dirs
58f8f89
Merge pull request #581 from JMackie80/master
9ba0aa0
Update README.md
1c59823
Update for 3.2.4 publish
e8539b7
Merge pull request #579 from leonardovillela/master
c8d815c
Improved error handling of env variables value parse
See the full diff