Open greenkeeper[bot] opened 8 years ago
After pinning to 6.4.0 your tests are passing again. Downgrade this dependency π.
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 7 commits .
e5613f0
chore(release): 6.6.0
19a897b
refactor: use process.stdout.columns instead of window-size (#737)
66573c8
feat: split demand() into demandCommand()/demandOption() (#740)
5883779
feat: implement conflicts() for defining mutually exclusive arguments; thanks @madcampos! (#741)
f755e27
fix: [object Object] was accidentally being populated on options object (#736)
27e1a57
feat: support for positional argument aliases (#727)
9bdaab7
fix: do not use cwd when resolving package.json for yargs parsing config (#726)
See the full diff.
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 44 commits .
e7359d6
chore(release): 7.1.0
c357412
docs: switch to conventional commits badge [ci skip] (#850)
17e89bd
fix: we shouldn't output help if we've printed a prior help-like message (#847)
50c9acd
chore: add editorconfig (#848)
360e301
fix: get terminalWidth in non interactive mode no longer causes a validation exception (#837)
fde0564
feat: add support for numeric commands (#825)
c748dd2
fix: fix demandOption no longer treats 'false' as truthy (#829)
e0b4efb
test: Made unit test passing with node-chakracore
8756a3c
chore(release): 7.0.2
fa86602
chore: fix test message
b3eb2fe
fix: populating placeholder arguments broke validation
82c7a4e
use console.log instead of util.print, fix #813
4df3a10
chore(release): 7.0.1
9c03fa4
fix: --help with default command should print top-level help (#810)
5334370
docs: env vars now take precedence over config file/objects (#808)
There are 44 commits in total. See the full diff.
Version 6.5.0 of yargs just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As yargs is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/timdp/cross-spawn-promise/build/126)Commits
The new version differs by 6 commits .
51af0a6
chore(release): 6.5.0
702995a
feat: pull in yargs-parser introducing additional settings (#688), and fixing #716 (#722)
30a9492
fix: still freeze/unfreeze if parse() is called in isolation (#717)
84c69cc
docs: use https for image URL at README.md (#718)
00d6513
chore(package): update nyc to version 10.0.0
6d17938
chore(package): update nyc to version 9.0.1
See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: