Skip to content

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

yargs just published its new version 6.6.0.

State Failing tests ⚠️
Dependency yargs
New version 6.6.0
Type dependency

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

It looks like your project, in its current form, is malfunctioning and this update didn’t really change that. I don’t want to leave you in the dark about updates though. I recommend you get your project passing and then check the impact of this update again.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


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.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants