New version of graphql (1.12.0) broke the build

[depfu]

👉 This PR is queued up to get rebased by Depfu

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
graphql	~> 1.9	1.12.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of graphql for this test run.

What changed?

✳️ graphql (~> 1.9 → 1.12.0) · Repo · Changelog

Release Notes

1.12.0 (from changelog)

Breaking changes

• GraphQL::Schema defaults to GraphQL::Execution::Interpreter, GraphQL::Analysis::AST, GraphQL::Pagination::Connections, and GraphQL::Execution::Errors. (#3145) To get the previous (deprecated) behaviors:

  # Revert to deprecated execution behaviors:
  use GraphQL::Execution::Execute
  use GraphQL::Analysis
  # Disable the new connection implementation:
  self.connections = nil

• GraphQL::Execution::Interpreter::Arguments instances are frozen (#3138). (Usually, GraphQL code doesn't interact with these objects, but they're used some places under the hood.)

Deprecations

• Many, many legacy classes and methods were deprecated. #3275 Deprecation errors include links to migration documentation. For a full list, see: #3056

New features

• Rails-like argument validations (#3207)
• Fiber-based GraphQL::Dataloader for batch-loading data #3264
• Connection and edge behaviors are available as mixins #3071
• Schema definition supports schema directives #3224

Bug fixes

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 8 commits:

• 1.12.0
• Merge pull request #3287 from rmosolgo/prep-1.12
• prepare 1.12.0
• remove RelayClassicMutation.return_interfaces
• Merge pull request #3286 from rmosolgo/1.12-dev
• Update another test
• Merge branch 'master' into 1.12-dev
• Merge pull request #3275 from rmosolgo/add-deprecations

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)