Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump graphql from 0.13.0 to 0.13.2 #388

Merged
merged 1 commit into from
Apr 3, 2018

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented Mar 19, 2018

Bumps graphql from 0.13.0 to 0.13.2.

Release notes

Sourced from graphql's releases.

v0.13.2

New:

  • Allow buildSchema() to take options (#1249)
  • Update to Flow v0.68 (#1290)

Fixes:

  • Update iterall (#1254)
  • buildSchema: Make options optional (#1270)

v0.13.1

New:

  • Publish .mjs files for module code to support native esmodules (#1244)
  • Interface type definitions may now be extended with extendSchema (#1222)
  • isValidNameError utility is now exported as a non-throwing alternative to assertValidName (#1237)
  • ExectuableDefinitionNode Flow type is now exported (#1241)

Fixes:

  • extendSchema now preserves (and allows extending) a list of legacy field names which would otherwise be considered invalid (#1235)
  • Replaced a misplaced licensing header (7e6898465131be522666bcbdf71d8c8f2d85e5d2)
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If you'd like to skip this version, you can just close this PR. If you have any feedback just mention @dependabot in the comments below.

@codecov
Copy link

codecov bot commented Mar 19, 2018

Codecov Report

Merging #388 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #388   +/-   ##
=======================================
  Coverage   99.43%   99.43%           
=======================================
  Files          26       26           
  Lines         178      178           
  Branches       15       15           
=======================================
  Hits          177      177           
  Misses          1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0cf59e8...23e14fd. Read the comment docs.

@phyrog
Copy link
Contributor

phyrog commented Mar 19, 2018

Blocked due to facebook/create-react-app#4085

@phyrog phyrog added the blocked label Mar 19, 2018
@dependabot-preview dependabot-preview bot force-pushed the dependabot/npm_and_yarn/graphql-0.13.2 branch 2 times, most recently from da2cc65 to 7b76b0a Compare March 30, 2018 18:08
@gaearon
Copy link

gaearon commented Apr 3, 2018

If your project is built with Create React App and not ejected, react-scripts@1.1.2 should fix this.
Here is how to upgrade:

https://github.com/facebook/create-react-app/releases/tag/v1.1.2

Otherwise you can apply a similar fix yourself in your project config. Cheers!

@phyrog
Copy link
Contributor

phyrog commented Apr 3, 2018

@gaearon Thanks for the heads up.

@dependabot rebase

Bumps [graphql](https://github.com/graphql/graphql-js) from 0.13.0 to 0.13.2.
- [Release notes](https://github.com/graphql/graphql-js/releases)
- [Commits](graphql/graphql-js@v0.13.0...v0.13.2)

Signed-off-by: dependabot[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot force-pushed the dependabot/npm_and_yarn/graphql-0.13.2 branch from 7b76b0a to 23e14fd Compare April 3, 2018 14:01
@phyrog phyrog merged commit c01b5e3 into master Apr 3, 2018
@phyrog phyrog deleted the dependabot/npm_and_yarn/graphql-0.13.2 branch April 3, 2018 14:18
@phyrog phyrog removed the blocked label Apr 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants