leecade / leecade/fe

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

Open
#27 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

greenkeeper
Dominant language
JavaScript
Stars
15
Forks
4
No merged PRs in 30d

Description

Version 6.4.0 of yargs just got published.

Branch Build failing 🚨
Dependency yargs
Current Version 6.3.0
Type dependency

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 💪

Status Details

  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v6.4.0
Bug Fixes
  • locales: correct some Russian translations (#691) (a980671)
Features
Performance Improvements
  • normalizing package data is an expensive operation (#705) (49cf533)
Commits

The new version differs by 10 commits .

  • bf6707e chore(release): 6.4.0
  • 8507390 chore: add camelcase to greenkeeper ignore, until we drop 0.10 support (#704)
  • 49cf533 perf: normalizing package data is an expensive operation (#705)
  • 8f4c7cf docs: nit, make test description reflect API, not application of API
  • 21b74f9 feat: yargs is now passed as the third-argument to fail handler (#613)
  • 54cb31d feat: update to yargs-parser that addresses #598, #617 (#700)
  • 8bbca63 chore(package): update cross-spawn to version 5.0.1
  • a980671 fix(locales): correct some Russian translations (#691)
  • 68dac1f feat(locales): Added Belarusian translation (#690)
  • 46ce1bb feat(locales): Create nl.json (#687)

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 🌴

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Greenkeeper yargs 6.4.0 comparison and the failed CircleCI and AppVeyor builds linked in the issue. Inspect the dependency declaration and CI failure output to identify what changed, then verify that the project builds and its tests pass with a compatible yargs version.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.