-
Notifications
You must be signed in to change notification settings - Fork 0
An in-range update of commander is breaking the build 🚨 #42
Comments
After pinning to 2.12.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 2.14.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 2.14.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.15.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.15.0
CommitsThe new version differs by 7 commits.
See the full diff |
Version 2.15.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.15.1fix #777 |
Version 2.16.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.16.0
CommitsThe new version differs by 17 commits.
There are 17 commits in total. See the full diff |
Version 2.17.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.17.0 |
Version 2.17.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.17.1
|
Version 2.18.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv2.18.0CommitsThe new version differs by 5 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v2.19.0CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v2.20.0
CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Version 2.13.0 of commander was just published.
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
Release Notes
v2.13.0Commits
The new version differs by 8 commits.
291fbaa
Merge pull request #748 from abetomo/version_bump_2.13.0
63f1ee9
version bump 2.13.0
f13ee18
Do not print default for --no-
ff712f1
remove trailing spaces in command help
fefda77
Merge pull request #713 from sveinburne/feature/enhanced-typedefs
d812171
Merge pull request #723 from abetomo/add_nodejs_version_to_ci_yml
498ce71
Update CI's Node.js to LTS and latest version
965188f
typedefs: Command and Option types added to commander namespace
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: