An in-range update of travis-deploy-once is breaking the build π¨
greenkeeper opened this issue Β· 3 comments
The devDependency travis-deploy-once was updated from 5.0.8
to 5.0.9
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
travis-deploy-once 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).
Release Notes for v5.0.9
5.0.9 (2018-09-27)
Bug Fixes
- use
require.resolve
to load babel preset (16292d3)
Commits
The new version differs by 2 commits.
16292d3
fix: use
require.resolve
to load babel preset858d475
test: add
babel-register.js
to test coverage
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.0.8 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependency
travis-deploy-once was updated from5.0.9
to5.0.10
.
Your tests are passing again with this update. Explicitly upgrade to this version π
- The
devDependency
travis-deploy-once was updated from5.0.10
to5.0.11
.
Your tests are passing again with this update. Explicitly upgrade to this version π