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

fix(deps): update dependency yargs to v14 #440

Merged
merged 1 commit into from
Aug 20, 2019
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 19, 2019

This PR contains the following updates:

Package Type Update Change
yargs (source) dependencies major 13.3.0 -> 14.0.0

Release Notes

yargs/yargs

v14.0.0

Compare Source

⚠ BREAKING CHANGES
  • we now only officially support yargs.$0 parameter and discourage direct access to yargs.parsed
  • previously to this fix methods like yargs.getOptions() contained the state of the last command to execute.
  • do not allow additional positionals in strict mode
Bug Fixes
Features

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot. View repository job log here.

@renovate renovate bot force-pushed the renovate/yargs-14.x branch from c934023 to 855ce30 Compare August 19, 2019 23:29
@coveralls
Copy link

coveralls commented Aug 19, 2019

Coverage Status

Coverage remained the same at 100.0% when pulling 855ce30 on renovate/yargs-14.x into a307562 on master.

@bcoe bcoe merged commit fe37e73 into master Aug 20, 2019
@bcoe bcoe deleted the renovate/yargs-14.x branch August 20, 2019 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants