An in-range update of pre-commit is breaking the build 🚨

[greenkeeper]

Version 1.2.1 of pre-commit just got published.

Branch	Build failing 🚨
Dependency	pre-commit
Current Version	1.2.0
Type	devDependency

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

As pre-commit 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 could not complete due to an error Details

• ✅ coverage/coveralls First build on greenkeeper/pre-commit-1.2.1 at 94.81% Details

Commits

The new version differs by 2 commits .

• 7d6feb1 [dist] 1.2.1
• 3ecafe0 [fix] chmod 0777 the newly created file; Fixes #88

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.2.0 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 1.2.2 just got published.

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

Commits

The new version differs by 2 commits .

• bf393ad [dist] 1.2.2
• 675560c Use string instead of int 777 in fs.chmodSync so it gets correctly interpreted as octal (#90)

See the full diff.