Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
greenkeeper bot opened this issue Aug 4, 2018 · 10 comments
Open

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

greenkeeper bot opened this issue Aug 4, 2018 · 10 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Aug 4, 2018

Version 5.0.2 of travis-deploy-once was just published.

Branch Build failing 🚨
Dependency travis-deploy-once
Current Version 5.0.1
Type devDependency

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 failed (Details).

Release Notes v5.0.2

5.0.2 (2018-08-04)

Bug Fixes

  • package: update got to version 9.0.0 (bec148c)
Commits

The new version differs by 2 commits.

  • bec148c fix(package): update got to version 9.0.0
  • 5649360 chore(package): update clear-module to version 3.0.0

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 Aug 4, 2018

After pinning to 5.0.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 24, 2018

Version 5.0.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v5.0.3

5.0.3 (2018-08-24)

Bug Fixes

  • package: update execa to version 0.11.0 (833916a)
Commits

The new version differs by 3 commits.

  • 0875628 chore(package): update got to version 9.1.0
  • 833916a fix(package): update execa to version 0.11.0
  • e40f304 chore(package): update xo to version 0.22.0

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 26, 2018

Version 5.0.4 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v5.0.4

5.0.4 (2018-08-26)

Bug Fixes

  • package: update execa to version 1.0.0 (91da1a0)
Commits

The new version differs by 1 commits.

  • 91da1a0 fix(package): update execa to version 1.0.0

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 29, 2018

Version 5.0.5 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v5.0.5

5.0.5 (2018-08-29)

Bug Fixes

  • package: update babel to version 7.0.0 (156b366)
Commits

The new version differs by 1 commits.

  • 156b366 fix(package): update babel to version 7.0.0

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 30, 2018

Version 5.0.6 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v5.0.6

5.0.6 (2018-08-30)

Bug Fixes

  • add babel-register file to npm package (21b59db)
Commits

The new version differs by 1 commits.

  • 21b59db fix: add babel-register file to npm package

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 30, 2018

Version 5.0.7 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes v5.0.7

5.0.7 (2018-08-30)

Bug Fixes

  • add babel-register.js file to npm package (c3da8f3)
Commits

The new version differs by 1 commits.

  • c3da8f3 fix: add babel-register.js file to npm package

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 19, 2018

Your tests are still failing with this version. Compare changes

Release Notes for v5.0.8

5.0.8 (2018-09-19)

Bug Fixes

  • fix babel-register config when module is globally installed (4697ad5)
Commits

The new version differs by 3 commits.

  • 4697ad5 fix: fix babel-register config when module is globally installed
  • 8105e60 chore(package): update nock to version 10.0.0
  • 43b48a3 chore(package): update xo to version 0.23.0

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 27, 2018

Your tests are still failing with this version. Compare changes

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 12, 2018

Your tests are still failing with this version. Compare changes

Release Notes for v5.0.10

5.0.10 (2018-12-12)

Bug Fixes

  • package: update p-retry to version 3.0.0 (b360e09)
Commits

The new version differs by 3 commits.

  • b360e09 fix(package): update p-retry to version 3.0.0
  • fe68469 chore(package): update nyc and sinon
  • 0f8d0d3 chore(package): update commitizen to version 3.0.0

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 15, 2018

Your tests are still failing with this version. Compare changes

Release Notes for v5.0.11

5.0.11 (2018-12-15)

Bug Fixes

  • readme: add deprecation notice (70e9057)
Commits

The new version differs by 1 commits.

  • 70e9057 fix(readme): add deprecation notice

See the full diff

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

No branches or pull requests

0 participants