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 minimist is breaking the build 🚨 #538

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

An in-range update of minimist is breaking the build 🚨 #538

greenkeeper bot opened this issue Mar 10, 2020 · 5 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 10, 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 dependency minimist was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

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

minimist is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 5 commits.

  • 29783cd 1.2.1
  • 6be5dae add test
  • ac3fc79 fix bad boolean regexp
  • 4cf45a2 Merge pull request #63 from lydell/dash-dash-docs-fix
  • 5fa440e move the opts['--'] example back where it belongs

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 10, 2020

  • The dependency minimist was updated from 1.2.1 to 1.2.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 10, 2020

After pinning to 1.2.0 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 10, 2020

  • The dependency minimist was updated from 1.2.2 to 1.2.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

  • 6457d74 1.2.3
  • 38a4d1c even more aggressive checks for protocol pollution
  • 13c01a5 more failing proto pollution tests

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 11, 2020

  • The dependency minimist was updated from 1.2.3 to 1.2.4.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 12, 2020

  • The dependency minimist was updated from 1.2.4 to 1.2.5.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 1 commits.

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