Skip to content
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

Open
greenkeeper bot opened this issue Mar 6, 2020 · 5 comments
Open

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 6, 2020


☝️ 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 to 1.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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • Travis CI - Branch: The build failed.

Release Notes for v1.9.3

1.9.3 (2020-03-06)

Bug Fixes

  • upgraded ggit to the latest version (f16d530)
  • upgraded ggit to the latest version (b0aa067)
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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 6, 2020

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.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 7, 2020

Your tests are still failing with this version. Compare changes

Release Notes for v1.9.4

1.9.4 (2020-03-07)

Bug Fixes

  • deps: update dependency update-notifier to v4 (0df9575)
Commits

The new version differs by 4 commits.

  • 0df9575 fix(deps): update dependency update-notifier to v4
  • 59ee694 ci(cache): used the more modern config for caching npm dependencies
  • e12fe75 chore(deps): pin dependency semantic-release to 17.0.4
  • 3523452 chore: add renovate file

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 12, 2020

Your tests are still failing with this version. Compare changes

Release Notes for v1.9.5

1.9.5 (2020-03-12)

Bug Fixes

  • deps: update dependency pluralize to v8 (b3dde2d)
Commits

The new version differs by 2 commits.

  • b3dde2d fix(deps): update dependency pluralize to v8
  • 7f140c3 trigger build

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 12, 2020

Your tests are still failing with this version. Compare changes

Release Notes for v1.9.6

1.9.6 (2020-03-12)

Bug Fixes

  • deps: update dependency ramda to v0.27.0 (0f5381f)
Commits

The new version differs by 1 commits.

  • 0f5381f fix(deps): update dependency ramda to v0.27.0

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 12, 2020

Your tests are still failing with this version. Compare changes

Release Notes for v1.9.7

1.9.7 (2020-03-12)

Bug Fixes

  • deps: update dependency bluebird to v3.7.2 (9f2b12c)
  • deps: update dependency debug to v4 (124c68b)
Commits

The new version differs by 4 commits.

  • 9f2b12c fix(deps): update dependency bluebird to v3.7.2
  • 124c68b fix(deps): update dependency debug to v4
  • 4319c43 chore(deps): update dependency rocha to v2.5.10
  • fc0589a chore(deps): update dependency babel-eslint to v8.2.6

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants