Skip to content

An in-range update of yargs is breaking the build 🚨 #46

@greenkeeper

Description

@greenkeeper

Version 6.5.0 of yargs just got published.

Branch Build failing 🚨
Dependency yargs
Current Version 6.4.0
Type devDependency

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 💪


Status Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details
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 and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions