greenkeeper[bot]
commented
8 years ago After pinning to 6.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Open greenkeeper[bot] opened 8 years ago
greenkeeper[bot]
commented
8 years ago After pinning to 6.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
8 years ago Your tests are passing again with this version. Explicitly upgrade to this version 🚀
The new version differs by 6 commits .
51af0a6 chore(release): 6.5.0702995a 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.06d17938 chore(package): update nyc to version 9.0.1See the full diff.
greenkeeper[bot]
commented
7 years ago Your tests are passing again with this version. Explicitly upgrade to this version 🚀
The new version differs by 13 commits .
e5613f0 chore(release): 6.6.019a897b 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)51af0a6 chore(release): 6.5.0702995a 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.06d17938 chore(package): update nyc to version 9.0.1See the full diff.
Version 6.4.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 a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **ci/circleci** CircleCI is running your tests [Details](https://circleci.com/gh/leecade/fe/66?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/leecade/fe/build/1.0.70)Release Notes
v6.4.0Bug Fixes
Features
Performance Improvements
Commits
The new version differs by 10 commits .
bf6707echore(release): 6.4.08507390chore: add camelcase to greenkeeper ignore, until we drop 0.10 support (#704)49cf533perf: normalizing package data is an expensive operation (#705)8f4c7cfdocs: nit, make test description reflect API, not application of API21b74f9feat: yargs is now passed as the third-argument to fail handler (#613)54cb31dfeat: update to yargs-parser that addresses #598, #617 (#700)8bbca63chore(package): update cross-spawn to version 5.0.1a980671fix(locales): correct some Russian translations (#691)68dac1ffeat(locales): Added Belarusian translation (#690)46ce1bbfeat(locales): Create nl.json (#687)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: