An in-range update of sanitize-filename is breaking the build 🚨

[greenkeeper]

The devDependency sanitize-filename was updated from 1.6.1 to 1.6.2.

🚨 View failing branch.

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

sanitize-filename 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

• ❌ semaphoreci: The build failed on Semaphore. (Details).

---

Commits

The new version differs by 6 commits.

• 9c750cd 1.6.2
• b5dd8fe Validate input is string (#51)
• 7f7517a Removed Repeated Colon from RegEx (#47)
• 6ecdad2 Improve CI testing (#50)
• 0d21bf1 Add documentation for replacement functions (#39)
• 76a0caa chore(package): update browserify to version 14.0.0 (#33)

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 1.6.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency sanitize-filename was updated from 1.6.2 to 1.6.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 88bba56 1.6.3
• 72f2664 Add TypeScript type definitions (#52)

See the full diff