Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 2.9.0 of qemu just got published.

Branch Build failing 🚨
Dependency qemu
Current Version 2.8.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 14 commits0.

  • c6e6ace 2.9.0
  • 511c2ce Updated path to QEmu sources
  • 788cecc Merge pull request #16 from NodeOS/greenkeeper/initial
  • 23d44d2 Update README.md
  • b5173b1 docs(readme): add Greenkeeper badge
  • c242e82 Merge Update_to_2.8.1 into master
  • ee21f84 Update to 2.8.1
  • 2d968a2 Minor clean-up
  • a8e61b8 Build aarch64 emulators
  • e7da097 Updated QEmu download URL
  • a85b691 Merge pull request #13 from NodeOS/greenkeeper-prebuild-6.0.0
  • cd8c345 chore(package): update prebuild to version 6.0.0
  • 3e45ee9 Merge pull request #14 from NodeOS/greenkeeper-prebuild-install-2.1.0
  • 0f2a8ab chore(package): update prebuild-install to version 2.1.0

false

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 🌴

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