This repository has been archived by the owner on Jun 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
An in-range update of commander is breaking the build 🚨 #67
Labels
Comments
After pinning to 2.17.1 your tests are passing again. Downgrade this dependency 📌. |
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 passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v2.20.0
CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for v4.1.1Fixed
CommitsThe new version differs by 241 commits.
There are 241 commits in total. See the full diff |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Version 2.18.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.18.0Commits
The new version differs by 5 commits.
54b7f14
version bump 2.18.0
713db77
Standardize help output (#853)
af17996
chmod 644 travis.yml
8bcc493
Merge pull request #849 from KillWolfVlad/feature/executeSubCommand-tsnode
bf47dcc
add support for execute typescript subcommand via ts-node
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: