exogen / exogen/foobot-graphql
An in-range update of express-graphql is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Version 0.6.6 of express-graphql just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | express-graphql |
| Current Version | 0.6.5 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
express-graphql 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
Release Notes
v0.6.6New
- Update to graphql v0.10.0.
Commits
The new version differs by 33 commits.
364db640.6.6f5f37b4Merge pull request #314 from wincent/glh/pretty1f1f2bdRemove lints that clash with prettier's preferences4b0bd25Add prettifiere4e42a8Merge pull request #313 from graphql/greenkeeper/flow-bin-0.47.00ceb73aFix long-line lint99f88dfFix Flow error introduced in 63ea52b0a3a4e9e0247c636239a6Update graphql dev dependencya418d9fFreshen yarn.lock365a866chore(package): update flow-bin to version 0.47.094bb325Merge pull request #312 from graphql/greenkeeper/graphql-0.10.041ec1d8chore(package): update graphql to version 0.10.0e0ca425Freshen yarn.lock56351ebMerge pull request #311 from graphql/greenkeeper/mocha-3.4.25958a41chore(package): update mocha to version 3.4.2
There are 33 commits in total.
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
Begin by reproducing the failed CircleCI build for express-graphql 0.6.6 and comparing it with the passing Travis build. Investigate the incompatibility introduced by its graphql 0.10.0 update; done means the project builds and its tests pass with a supported dependency version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript
- Domain
- api, backend, 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