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

[greenkeeper]

The devDependency graphql was updated from 14.3.0 to 14.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

graphql is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v14.3.1

14.3.1 (2019-05-23)

Bug Fix 🐞

• #1809 buildClientSchema: include standard type only if it is used (@IvanGoncharov)

Polish 💅

19 PRs were merged

• #1899 findBreakingChanges: Add new tests to improve coverage (@IvanGoncharov)
• #1898 findBreakingChanges: simplify checking of wrapped types (@IvanGoncharov)
• #1897 findBreakingChanges-test: Remove unnecessary fields (@IvanGoncharov)
• #1896 findBreakingChanges: Correctly document not reachable statement (@IvanGoncharov)
• #1895 findBreakingChanges: Remove 'export' from internal functions (@IvanGoncharov)
• #1893 findBreakingChanges: test only functions that are part of public API (@IvanGoncharov)
• #1891 findBreakingChanges-test: remove unneeded 'Query' types (@IvanGoncharov)
• #1888 Enable 'no-prototype-builtins' ESLint rule (@IvanGoncharov)
• #1887 Enable "no-case-declarations" ESLint rule (@IvanGoncharov)
• #1885 Explicitly create Promise using "Promise.resolve" (@IvanGoncharov)
• #1884 memoize3: Explicitly pass arguments (@IvanGoncharov)
• #1883 Enable "no-sequences" ESLint rule (@IvanGoncharov)
• #1882 Enable 'prefer-promise-reject-errors' ESLint rule (@IvanGoncharov)
• #1881 Partly fix results of "sketchy-null-mixed" Flow check (@IvanGoncharov)
• #1880 Enable "sketchy-null-mixed" Flow check (@IvanGoncharov)
• #1879 Use "isPromise" instead of testing for 'then' property (@IvanGoncharov)
• #1866 Enable Flow in "visitor-test.js" (@IvanGoncharov)
• #1865 Enable Flow on "subscribe-test.js" (@IvanGoncharov)
• #1863 Fix some typos in stripIgnoredCharacters docs+tests (@Cito)

Internal 🏠

15 PRs were merged

• #1892 build: Add new lines to ".js" and ".mjs" files (@IvanGoncharov)
• #1886 Remove TODO on "no-warning-comments" ESLint rule (@IvanGoncharov)
• #1877 Rename 'fs-utils.js' to 'utils.js' (@IvanGoncharov)
• #1875 Enable prettier for "resources/*.js" files (@IvanGoncharov)
• #1876 inline-invariant: use template instead of AST (@IvanGoncharov)
• #1874 Enable "no-inner-declarations" rule on "resources/*.js" files (@IvanGoncharov)
• #1873 Fix lint issues in 'resources/*.js' files (@IvanGoncharov)
• #1872 Replace all "var" with "const" & "let" in "resources/*.js" files (@IvanGoncharov)
• #1871 Lint JS files inside "resources" folder (@IvanGoncharov)
• #1870 Add missing "use strict" (@IvanGoncharov)
• #1869 ESLint: remove useless "parserOptions" options (@IvanGoncharov)
• #1868 Add missing "@noflow" (@IvanGoncharov)
• #1867 ESLint: Simplify exclude for "no-restricted-syntax" rule (@IvanGoncharov)
• #1864 Drop parser option since Prettier supports Flow by default (@IvanGoncharov)
• #1855 Add 'yarn check --integrity' to CI tests (@IvanGoncharov)

Committers: 2

• Christoph Zwerschke (@Cito)
• Ivan Goncharov (@IvanGoncharov)

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 14.3.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.