An in-range update of steal-tools is breaking the build 🚨

[greenkeeper]

Version 1.3.6 of steal-tools just got published.

Branch	Build failing 🚨
Dependency	steal-tools
Current Version	1.3.5
Type	devDependency

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

As steal-tools 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

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 25 commits.

• 1b01f1d 1.3.6
• 6616335 Merge pull request #756 from stealjs/eng
• 7202d09 Update engines field in package.json
• c2df0b1 Merge pull request #750 from stealjs/docs/uglify-options
• 0b17eca documented uglifyOptions with an example
• 95e4699 Merge pull request #739 from stealjs/condition-eval
• c2fb57e Update steal-conditional version
• 325e3ac Test conditional using browser specific code
• 910fdcb Merge pull request #738 from stealjs/recycle-tests
• 04a44d8 Run recycle tests in Node V8
• 808fdd6 Merge pull request #737 from stealjs/greenkeeper/mock-fs-4.4.1
• 68c010d Merge pull request #736 from stealjs/issue/727-extra-space
• bcff2a3 enabled clean_test
• a561b88 Allow extra space before steal-remove-start and -end tags to support standard linting. #727
• fec0b64 chore(package): update mock-fs to version 4.4.1

There are 25 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 🌴

[greenkeeper]

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