Skip to content
This repository has been archived by the owner on Jun 24, 2024. It is now read-only.

An in-range update of travis-deploy-once is breaking the build 🚨 #134

Open
greenkeeper bot opened this issue Sep 27, 2018 · 1 comment
Open

An in-range update of travis-deploy-once is breaking the build 🚨 #134

greenkeeper bot opened this issue Sep 27, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Sep 27, 2018

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 preset
  • 858d475 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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 27, 2018

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants