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-core from 2.2.1 to 3.1.1 #1684

Closed
wants to merge 1 commit into from

Conversation

dependabot-preview[bot]
Copy link
Contributor

@dependabot-preview dependabot-preview bot commented May 18, 2020

Bumps graphql-core from 2.2.1 to 3.1.1.

Release notes

Sourced from graphql-core's releases.

v3.1.0

Final release of GraphQL-core v3.1.0, based on GraphQL.js v15.0.0.

See the three pre-releases v3.1.0b0, v3.1.0b1 and v3.1.0b2 for a complete list of changes.

v3.1.0b2

Third beta release of GraphQL-core 3.1, based on GraphQL.js v15.0.0rc2.

In addition to incorporating the latest changes from the master branch of GraphQL.js, this release also contains the following improvements:

  • Increased performance by using a faster isawaitable() function (#54).
  • Nodes and some other objects are now extensible and weak-referencable (#82).

We also renamed the repository on GitHub from graphql-python/graphql-core-next to graphql-python/graphql-core.

Contributors to this release were:

@Cito, @astronouth7303, @Hellzed and @qeternity

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3.1 release.

v3.1.0b1

Second beta release of GraphQL-core 3.1, based on GraphQL.js v15.0.0rc2.

In addition to incorporating the latest changes in GraphQL.js v15.0.0rc2, this release also contains the following improvements and changes:

  • Following a change in GraphQL.js to keep the order of user provided types, the type map reducer for the GraphQLSchema has been removed.
  • We now support inheritance when evaluating the __typename attribute (#25).
  • FieldNodes and InputValueNodes are now only DefinitionNodes, not TypeDefinitionNodes.
  • The test suite now has 100% coverage, and less coverage will count as failure.

Contributors to this release were:

@Cito, @Hellzed

Thanks to everybody who contributed by sending bug reports or pull requests. Please continue to report any problems you find in this beta release, so that these can be fixed in the final v3.1 release.

v3.1.0b0

First beta release of GraphQL-core 3.1, based on GraphQL.js v15.0.0rc1.

In addition to incorporating the latest changes from GraphQL.js (see the list of changes in GraphQL.js v15.0.0a1, v15.0.0a2 and v15.0.0rc1), this release also contains the following improvements and changes:

  • Change: Use Undefined instead of INVALID which is now deprecated (#77)
  • Use explicit Optional type on arguments (#76)
  • Remove unnecessary result type annotation from __init__ methods (Make return type implicitly None for type checked __init__ and __init_subclass__ python/mypy#5677)
  • Better docstring for ast_from_value
  • Better docstring for lexicographic_sort_schema (#75)
  • Fixed a minor issue when coverting lists in ast_from_value()
  • Fixed a minor issue with MapAsyncIterator.athrow()
  • Improved test coverage (trying to reach 100% for final release)
... (truncated)
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 all status checks pass Dependabot will automatically merge this pull request.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels May 18, 2020
@dependabot-preview
Copy link
Contributor Author

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/graphql-core-3.1.1 branch from 2ba4627 to 9675fc3 Compare June 16, 2020 02:20
@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/graphql-core-3.1.1 branch from 9675fc3 to ebfe2df Compare June 29, 2020 15:17
@dependabot-preview dependabot-preview bot force-pushed the dependabot/pip/graphql-core-3.1.1 branch from ebfe2df to badb422 Compare June 29, 2020 23:12
@dependabot-preview
Copy link
Contributor Author

Superseded by #1789.

@dependabot-preview dependabot-preview bot deleted the dependabot/pip/graphql-core-3.1.1 branch July 6, 2020 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants