An in-range update of aegir is breaking the build 🚨

[greenkeeper]

Version 9.3.2 of aegir just got published.

Branch	Build failing 🚨
Dependency	aegir
Current Version	9.3.1
Type	devDependency

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

As aegir 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

• ✅ ci/circleci Your tests passed on CircleCI! Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

• ✅ coverage/coveralls First build on greenkeeper/aegir-9.3.2 at 96.875% Details

Release Notes

v9.3.2

Features

• deps: use new browserify-zlib-next package (68810c1)

Commits

The new version differs by 5 commits .

• e501ba3 chore: release version v9.3.2
• 73d2f9c chore: update contributors
• 68810c1 feat(deps): use new browserify-zlib-next package
• a1a0753 Merge pull request #93 from dignifiedquire/greenkeeper/update-all
• f3e6620 chore(package): update dependencies

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 🌴

[greenkeeper]

After pinning to 9.3.1 your tests are passing again. Downgrade this dependency 📌.