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 commander is breaking the build 🚨 #102

Open
greenkeeper bot opened this issue Oct 8, 2018 · 2 comments
Open

An in-range update of commander is breaking the build 🚨 #102

greenkeeper bot opened this issue Oct 8, 2018 · 2 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Oct 8, 2018

The dependency commander was updated from 2.18.0 to 2.19.0.

🚨 View failing branch.

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

commander 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
  • ci/circleci: Your tests passed on CircleCI! (Details).
  • coverage/coveralls: First build on greenkeeper/commander-2.19.0 at 12.808% (Details).
  • continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).
  • codecov/project: No report found to compare against (Details).
  • Build: Google Cloud Platform project is not set up correctly for this GitHub app. Please reinstall the app and go through the setup flow again.

Release Notes for v2.19.0
  • Removed newline after Options and Commands headers (#864)
  • Bugfix - Error output (#862)
  • Fix to change default value to string (#856)
Commits

The new version differs by 6 commits.

  • 78b7dbd version bump 2.19.0
  • 6aafa20 prefixed error messages with "error:"
  • 6c0c1f6 removed newline above and below errors
  • b6549f2 removed indentation from errors
  • 2c20e91 removed newline after options and commands headers
  • 4c294c1 Fix to change default value to string

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
Author

greenkeeper bot commented Oct 8, 2018

After pinning to 2.18.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
Author

greenkeeper bot commented Apr 3, 2019

  • The dependency commander was updated from 2.19.0 to 2.20.0.

Your tests are still failing with this version. Compare changes

Release Notes for v2.20.0
  • fix: resolve symbolic links completely when hunting for subcommands (#935)
  • Update index.d.ts (#930)
  • Update Readme.md (#924)
  • Remove --save option as it isn't required anymore (#918)
  • Add link to the license file (#900)
  • Added example of receiving args from options (#858)
  • Added missing semicolon (#882)
  • Add extension to .eslintrc (#876)
Commits

The new version differs by 18 commits.

  • 3e8bf54 Merge pull request #946 from abetomo/version_bump_2.20.0
  • 1ffcbef version bump 2.20.0
  • 50922d8 Merge pull request #935 from MarshallOfSound/fix-deep-sym-link-resolution
  • 994d24d fix: resolve symbol links until their are no more symbolic links
  • 291fc04 Merge pull request #930 from kira1928/update-index.d.ts
  • a469137 some more fix.
  • a679949 Refine variable name. Use strict type definition instead of
  • e31bb8a Update index.d.ts
  • 4542306 Merge pull request #924 from ForJing/patch-1
  • 77bb580 Update Readme.md
  • 68545af Remove --save option as it isn't required anymore
  • 82d0d0a fix url :construction:
  • cec57f5 Add link to the license file :+1:
  • d240081 Update Readme.md
  • 03f7d38 Added example of receiving args from options

There are 18 commits in total.

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