An in-range update of babel-cli is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 6.24.1 of babel-cli just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-cli |
| Current Version | 6.24.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-cli 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
-
✅ coverage/coveralls First build on greenkeeper/babel-cli-6.24.1 at 12.808% Details
-
✅ ci/circleci Your tests passed on CircleCI! Details
-
✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
-
✅ codecov/patch Coverage not affected when comparing fe5bfde...a7c9aba Details
-
❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the greenkeeper/babel-cli-6.24.1 comparison branch and the linked CI and coverage status details. Investigate why babel-cli 6.24.1 is reported as breaking the build despite the listed passing checks, then verify the project build and coverage checks succeed with the dependency state resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100