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 @ava/babel is breaking the build 🚨 #41

Open
greenkeeper bot opened this issue Feb 9, 2020 · 1 comment
Open

An in-range update of @ava/babel is breaking the build 🚨 #41

greenkeeper bot opened this issue Feb 9, 2020 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Feb 9, 2020

The devDependency @ava/babel was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@ava/babel 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 is in progress (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: publish-test: Your tests failed on CircleCI (Details).

Release Notes for 1.0.1
  • Ensure pre-compiled .cjs files can be loaded, with thanks to @gloryofrobots

v1.0.0...v1.0.1

Commits

The new version differs by 5 commits.

  • a599a28 1.0.1
  • 801c73c XO: Temporarily disable import/order rule
  • 775114b Update require-precompiled
  • 7df10bb Update dependencies
  • b2a3676 Add code of conduct, contributing guide, issue templates

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 Feb 9, 2020

After pinning to 1.0.0 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 join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants