Skip to content

chore(deps): bump graphql-tools from 6.0.9 to 7.0.3 #502

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

Closed

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps graphql-tools from 6.0.9 to 7.0.3.

Release notes

Sourced from graphql-tools's releases.

@graphql-tools/[email protected]

Patch Changes

  • 718eda30: fix(stitch): fix mergeExternalObject regressions

    v7 introduced a regression in the merging of ExternalObjects that causes type merging to fail when undergoing multiple rounds of merging.

  • Updated dependencies [718eda30]

@graphql-tools/[email protected]

Patch Changes

  • 856e23fa: fix(delegate): WrapConcreteTypes should not process fragments that are not on a root type (#2173)
  • Updated dependencies [e3176633]

@graphql-tools/[email protected]

Patch Changes

  • a74f885c: links should behave like other packages when releasing and not publish new versions with minor updates of internal dependencies
  • Updated dependencies [856e23fa]
  • Updated dependencies [e3176633]

@graphql-tools/[email protected]

Patch Changes

[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

  • fcbc497b: fix(stitch): support type merging with abstract types (#2137)

... (truncated)

Changelog

Sourced from graphql-tools's changelog.

7.0.3

Patch Changes

7.0.2

Patch Changes

  • fb14cd28: Added export from new optimize package
  • Updated dependencies [fb14cd28]

7.0.1

Patch Changes

7.0.0

Major Changes

  • a9254491: - Resolver validation options should now be set to error, warn or ignore rather than true or false. In previous versions, some of the validators caused errors to be thrown, while some issued warnings. This changes brings consistency to validator behavior.

    • The allowResolversNotInSchema has been renamed to requireResolversToMatchSchema, to harmonize the naming convention of all the validators. The default setting of requireResolversToMatchSchema is error, matching the previous behavior.
    • The delegateToSchema return value has matured and been formalized as an ExternalObject, in which all errors are integrated into the GraphQL response, preserving their initial path. Those advanced users accessing the result directly will note the change in error handling. This also allows for the deprecation of unnecessary helper functions including slicedError, getErrors, getErrorsByPathSegment functions. Only external errors with missing or invalid paths must still be preserved by annotating the remote object with special properties. The new getUnpathedErrors function is therefore necessary for retrieving only these errors. Note also the new annotateExternalObject and mergeExternalObjects functions, as well as the renaming of handleResult to resolveExternalValue.

    • Transform types and the applySchemaTransforms are now relocated to the delegate package; applyRequestTransforms/applyResultTransforms functions have been deprecated, however, as this functionality has been replaced since v6 by the Transformer abstraction.

    • The transformRequest/transformResult methods are now provided additional delegationContext and transformationContext arguments -- these were introduced in v6, but previously optional.

    • The transformSchema method may wish to create additional delegating resolvers and so it is now provided the subschemaConfig and final (non-executable) transformedSchema parameters. As in v6, the transformSchema is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executabel) initial result. In v7, the individual transformSchema methods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.

... (truncated)

Commits
  • 179dd27 chore(release): update monorepo packages versions (#2545)
  • 0b8b116 fix(deps): update dependency tslib to ~2.1.0 (#2443)
  • 7eadc28 Use repository.packages in package.json files (#2316)
  • 8652e87 Upcoming Release Changes (#2271)
  • fb14cd2 Fixes for optimize package (#2270)
  • b9d75d2 [deploy_website] chore(release): update monorepo packages versions (#2139)
  • 9f42d2c chore(release): update monorepo packages versions (#2134)
  • a925449 fix(release): properly release v7
  • 69d8499 chore(release): update monorepo packages versions (#2132)
  • 96a7555 fix(release): don't transitively update to v7 (#2131)
  • Additional commits viewable in compare view

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.


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 the dependencies Pull requests that update a dependency file label Feb 11, 2021
@dependabot-preview
Copy link
Contributor Author

Superseded by #509.

@dependabot-preview dependabot-preview bot deleted the dependabot/npm_and_yarn/graphql-tools-7.0.3 branch February 18, 2021 04:22
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants