New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of ban-sensitive-files is breaking the build 🚨 #23
Comments
After pinning to 1.9.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io
The devDependency ban-sensitive-files was updated from
1.9.2
to1.9.3
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
ban-sensitive-files 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
Release Notes for v1.9.3
1.9.3 (2020-03-06)
Bug Fixes
Commits
The new version differs by 4 commits.
4e92e36
update semantic release
0d16000
update deps
f16d530
fix: upgraded ggit to the latest version
b0aa067
fix: upgraded ggit to the latest version
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 🌴
The text was updated successfully, but these errors were encountered: