Skip to content

An in-range update of qemu is breaking the build 🚨 #18

Description

@greenkeeper

Version 2.7.0 of qemu just got published.

Branch Build failing 🚨
Dependency qemu
Current Version 2.6.0
Type devDependency

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

As qemu is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • semaphoreci The build failed on Semaphore. Details
Commits

The new version differs by 20 commits .

  • df64e87 Merge Update_to_2.7.0 into master
  • 81f6000 Update to 2.7.0
  • 54d0ff4 Fixed badly binded function on prepublish script
  • acb967d Added missing ci-publish dependency
  • e70b4ae Auto-update using buho
  • b0b91c7 Merge pull request #7 from NodeOS/greenkeeper-update-all
  • e5c7f22 chore(package): update dependencies
  • d15f886 Merge pull request #5 from joshgarde/master
  • 5f87b64 Travis Update v2
  • faa1a6b Travis Update
  • 9716af6 platform fix
  • 8fe32d1 Merge pull request #2 from joshgarde/osx-support
  • 0416708 Travis Port - v1.0
  • b74d45e Code cleanup
  • 81f7084 Introducing OSX Support!

There are 20 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions