An in-range update of node-appc is breaking the build 🚨

[greenkeeper]

The dependency node-appc was updated from 0.3.2 to 0.3.3.

🚨 View failing branch.

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

node-appc is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/jenkins/branch: The build of this commit was aborted (Details).

---

Commits

The new version differs by 15 commits.

• bc3a5e0 chore(release): bump to 0.3.3
• 48d6b37 fix(module): if platform is ios fallback to iphone in moduleAPIVersion
• 9cb8dd2 fix(module): parse apiversions to integer before comparing
• 37e5f90 chore(package): update husky to version 3.0.0 (#170)
• 4b3ba3c chore(package): update lint-staged to version 9.0.0 (#169)
• a0218f7 Update danger to the latest version 🚀 (#164)
• 3b358ac style: fix eslint issue
• 8ab7602 chore(package): update lockfile package-lock.json
• 2e90138 chore(package): update mocha-jenkins-reporter to version 0.4.1
• 5d65c1a chore(package): update lockfile package-lock.json
• 979b227 chore(package): update eslint to version 5.16.0
• fc64bb0 chore(package): update lockfile package-lock.json
• 3e402ee chore(package): update husky to version 2.1.0
• 9c0d1ac chore(package): update lockfile package-lock.json
• 4bb0791 chore(package): update mocha to version 6.0.2

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]

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

[ewanharris]

Done in #11025 and #11026