An in-range update of nps is breaking the build π¨
greenkeeper opened this issue Β· 5 comments
The devDependency nps was updated from 5.9.5
to 5.9.6
.
This version is covered by your current version range and after updating it in your project the build failed.
nps 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
β continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
Commits
The new version differs by 8 commits.
ecb5c43
ci: π‘ Remove semantic release
835ffaa
ci: π‘ npm release config tweak
05680db
style: π new prettier formatting
f3dfdc3
chore: π€ update urls to new nps github repo
3545a00
ci: π‘ enable automated NPM publishes
f9f5ca4
chore(contributors): add effervescentia
0de42c8
feat: support .npsrc file for cli config
1d23198
chore(readme): add details about .npsrc file
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
After pinning to 5.9.5 your tests are passing again. Downgrade this dependency
- The
devDependency
nps was updated from5.9.6
to5.9.7
.
Your tests are still failing with this version. Compare changes
- The
devDependency
nps was updated from5.9.7
to5.9.8
.
Your tests are passing again with this update. Explicitly upgrade to this version
- The
devDependency
nps was updated from5.9.8
to5.9.10
.
Your tests are still failing with this version. Compare changes
- The
devDependency
nps was updated from5.9.10
to5.9.12
.
Your tests are passing again with this update. Explicitly upgrade to this version
Release Notes for v5.9.12 (2019-12-07)
Release to sync version numbers on npmjs.com and Github. Replaces the broken deploy v5.9.10.