An in-range update of babel-eslint 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 7.1.1 of babel-eslint just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-eslint |
| Current Version | 7.1.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-eslint 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
Commits
The new version differs by 5 commits .
-
bc482f47.1.1 -
baeb99bchore(package): update dependencies (#422) -
2d587d6append code frame on parse error (#418) -
e7c9a03chore(package): update babylon to version 6.13.0 (#420) -
971c8d6chore(package): update eslint to version 3.9.1 (#419)
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
- 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 branch for babel-eslint 7.1.1 and inspect the failed CircleCI and AppVeyor builds, comparing them with the current 7.1.0 dependency. Determine which of the five upstream commits causes the failure; done means the dependency setup and build checks pass again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- build-system, ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100