An in-range update of @types/ramda is breaking the build 🚨

[greenkeeper]

Version 0.25.37 of @types/ramda was just published.

Branch	Build failing 🚨
Dependency	@types/ramda
Current Version	0.25.36
Type	devDependency

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

@types/ramda 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

• ✅ ci/circleci: dependencies: Your tests passed on CircleCI! (Details).
• ❌ ci/circleci: build_and_test: Your tests failed on CircleCI (Details).
• ✅ ci/circleci: lint: Your tests passed on CircleCI! (Details).

---

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]

Version 0.25.38 just got published.

Your tests for group default are passing again with this version. Explicitly upgrade default to this version 🚀

[greenkeeper]

• The devDependency @types/ramda was updated from 0.25.38 to 0.25.39.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

[greenkeeper]

• The devDependency @types/ramda was updated from 0.25.39 to 0.25.40.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

[greenkeeper]

• The devDependency @types/ramda was updated from 0.26.0 to 0.26.1.

Your tests for group default are passing again with this update. Explicitly upgrade default to this version 🚀

[greenkeeper]

• The devDependency @types/ramda was updated from 0.26.2 to 0.26.3.

Your tests are still failing with this version. Compare changes