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

Update dependency graphql-tools to v9 #331

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 21, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-tools (source) 4.0.8 -> 9.0.1 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

ardatan/graphql-tools (graphql-tools)

v9.0.1

Compare Source

Patch Changes

v9.0.0

Compare Source

Major Changes
Patch Changes

v8.3.20

Compare Source

Patch Changes

v8.3.19

Compare Source

Patch Changes

v8.3.18

Compare Source

Patch Changes

v8.3.17

Compare Source

Patch Changes

v8.3.16

Compare Source

Patch Changes

v8.3.15

Compare Source

Patch Changes

v8.3.14

Compare Source

Patch Changes

v8.3.13

Compare Source

Patch Changes

v8.3.12

Compare Source

Patch Changes

v8.3.11

Compare Source

Patch Changes

v8.3.10

Compare Source

Patch Changes

v8.3.9

Compare Source

Patch Changes

v8.3.8

Compare Source

Patch Changes

v8.3.7

Compare Source

Patch Changes

v8.3.6

Compare Source

Patch Changes

v8.3.5

Compare Source

Patch Changes

v8.3.4

Compare Source

Patch Changes

v8.3.3

Compare Source

Patch Changes

v8.3.2

Compare Source

Patch Changes

v8.3.1

Compare Source

Patch Changes

v8.3.0

Compare Source

Minor Changes
  • d76a299: Support TypeScript module resolution.
Patch Changes

v8.2.13

Compare Source

Patch Changes

v8.2.12

Compare Source

Patch Changes

v8.2.11

Compare Source

Patch Changes

v8.2.10

Compare Source

Patch Changes

v8.2.9

Compare Source

Patch Changes

v8.2.8

Compare Source

Patch Changes

v8.2.7

Compare Source

Patch Changes

v8.2.6

Compare Source

Patch Changes

v8.2.5

Compare Source

Patch Changes

v8.2.4

Compare Source

Patch Changes

v8.2.3

Compare Source

Patch Changes

v8.2.2

Compare Source

Patch Changes

v8.2.1

Compare Source

Patch Changes

v8.2.0

Compare Source

Minor Changes
  • c5b0719: feat: GraphQL v16 support
Patch Changes

v8.1.0

Compare Source

Minor Changes

v8.0.0

Compare Source

Major Changes
  • 7d3e300: BREAKING CHANGE
    • Now it only exports makeExecutableSchema from @graphql-tools/schema
    • Please migrate to scoped packages(@graphql-tools/*) because this npm package will no longer get updated
Patch Changes

v7.0.5

Compare Source

Patch Changes

v7.0.4

Compare Source

Patch Changes
  • Revert mock package to v7 to avoid breaking changes

v7.0.3

Compare Source

Patch Changes

v7.0.2

Compare Source

Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes
  • a925449: - 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-executable) 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.

    • applySchemaTransforms parameters have been updated to match and support the transformSchema parameters above.

    • wrapSchema and generateProxyingResolvers now only take a single options argument with named properties of type SubschemaConfig. The previously possible shorthand version with first argument consisting of a GraphQLSchema and second argument representing the transforms should be reworked as a SubschemaConfig object.

    • Similarly, the ICreateProxyingResolverOptions interface that provides the options for the createProxyingResolver property of SubschemaConfig options has been adjusted. The schema property previously could be set to a GraphQLSchema or a SubschemaConfig object. This property has been removed in favor of a subschemaConfig property that will always be a SubschemaConfig object. The transforms property has been removed; transforms should be included within the SubschemaConfig object.`

    • The format of the wrapping schema has solidified. All non-root fields are expected to use identical resolvers, either defaultMergedResolver or a custom equivalent, with root fields doing the hard work of proxying. Support for custom merged resolvers throught createMergedResolver has been deprecated, as custom merging resolvers conflicts when using stitching's type merging, where resolvers are expected to be identical across subschemas.

    • The WrapFields transform's wrappingResolver option has been removed, as this complicates multiple wrapping layers, as well as planned functionality to wrap subscription root fields in potentially multiple layers, as the wrapping resolvers may be different in different layers. Modifying resolvers can still be performed by use of an additional transform such as TransformRootFields or TransformObjectFields.

    • The ExtendSchema transform has been removed, as it is conceptually simpler just to use stitchSchemas with one subschema.

    • The ReplaceFieldsWithFragment, AddFragmentsByField, AddSelectionSetsByField, and AddMergedTypeSelectionSets transforms has been removed, as they are superseded by the AddSelectionSets and VisitSelectionSets transforms. The AddSelectionSets purposely takes parsed SDL rather than strings, to nudge end users to parse these strings at build time (when possible), rather than at runtime. Parsing of selection set strings can be performed using the parseSelectionSet function from @graphql-tools/utils.

    • stitchSchemas's mergeTypes option is now true by default! This causes the onTypeConflict option to be ignored by default. To use onTypeConflict to select a specific type instead of simply merging, simply set mergeTypes to false.

    • schemas argument has been deprecated, use subschemas, typeDefs, or types, depending on what you are stitching.

    • When using batch delegation in type merging, the argsFromKeys function is now set only via the argsFromKeys property. Previously, if argsFromKeys was absent, it could be read from args.

    • Support for fragment hints has been removed in favor of selection set hints.

    • stitchSchemas now processes all GraphQLSchema and SubschemaConfig subschema input into new Subschema objects, handling schema config directives such aso@computed as well as generating the final transformed schema, stored as the transformedSchema property, if transforms are used. Signatures of the onTypeConflict, fieldConfigMerger, and inputFieldConfigMerger have been updated to include metadata related to the original and transformed subschemas. Note the property name change for onTypeConflict from schema to subschema.

    • Mocks returning objects with fields set as functions are now operating according to upstream graphql-js convention, i.e. these functions take three arguments, args, context, and info with parent available as this rather than as the first argument.
    • filterSchema's fieldFilter will now filter all fields across Object, Interface, and Input types. For the previous Object-only behavior, switch to the objectFieldFilter option.
    • Unused fieldNodes utility functions have been removed.
    • Unused typeContainsSelectionSet function has been removed, and typesContainSelectionSet has been moved to the stitch package.
    • Unnecessary Operation type has been removed in favor of OperationTypeNode from upstream graphql-js.
    • As above, applySchemaTransforms/applyRequestTransforms/applyResultTransforms have been removed from the utils package, as they are implemented elsewhere or no longer necessary.
Patch Changes

v6.2.6

Compare Source

Patch Changes

v6.2.5

Compare Source

Patch Changes

v6.2.4

Compare Source

Patch Changes

v6.2.3

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

  • Update dependencies

🚀 Features

v6.2.2

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.2.1

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.2.0

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🐛 Bug Fixes

v6.1.0

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.0.18

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

✏️ Docs

🧰 Enhancements

v6.0.17

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🐛 Bug Fixes

v6.0.16

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.0.15

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🧰 Enhancements

🐛 Bug Fixes

v6.0.14

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🧰 Enhancements

  • feat(merge): support multidimensional arrays for mergeTypeDefs and mergeResolvers @​ardatan (#​1789)

🐛 Bug Fixes

v6.0.13

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🧰 Enhancements

🐛 Bug Fixes

v6.0.12

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🐛 Bug Fixes

v6.0.11

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🐛 Bug Fixes

v6.0.10

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🐛 Bug Fixes


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 542a221 to 777b592 Compare June 25, 2020 22:53
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 777b592 to 1c1734c Compare July 2, 2020 13:12
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 78a7ad6 to 18df876 Compare July 16, 2020 12:43
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 18df876 to b1e9b03 Compare July 22, 2020 20:11
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 3 times, most recently from 44d98e7 to 9e4d5f1 Compare August 11, 2020 13:28
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 70c1455 to ed58f7c Compare September 1, 2020 08:43
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from ed58f7c to b87f7b1 Compare September 4, 2020 16:08
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from db8aaa6 to 0112d40 Compare September 19, 2020 08:20
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 7d36c63 to 472c38b Compare October 7, 2020 03:56
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 3 times, most recently from 68d0e96 to c606308 Compare October 24, 2020 20:39
@renovate renovate bot changed the title Update dependency graphql-tools to v6 Update dependency graphql-tools to v7 Oct 24, 2020
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from c606308 to df0fc08 Compare October 27, 2020 02:05
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from df0fc08 to 50ea0df Compare November 25, 2020 18:42
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 50ea0df to d6b849b Compare February 11, 2021 09:43
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from d6b849b to 59dcb95 Compare April 26, 2021 18:21
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 59dcb95 to f1f239e Compare May 16, 2021 00:07
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from f1f239e to 9aed8d6 Compare May 29, 2021 08:44
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 9aed8d6 to 09490e7 Compare July 28, 2021 10:59
@renovate renovate bot changed the title Update dependency graphql-tools to v7 Update dependency graphql-tools to v8 Jul 28, 2021
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 09490e7 to a5f7ea6 Compare August 4, 2021 15:00
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from a5f7ea6 to d5e37d2 Compare August 31, 2021 14:54
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from d5e37d2 to f28c1e8 Compare June 24, 2022 03:09
@renovate
Copy link
Contributor Author

renovate bot commented Jun 24, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: packages/web/package-lock.json
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@olimat%2fapi - Not found
npm ERR! 404 
npm ERR! 404  '@olimat/api@0.0.1' is not in this registry.
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-23T15_35_42_828Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from f28c1e8 to 4942cec Compare June 27, 2022 12:33
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 4942cec to 7f2a09b Compare July 27, 2022 21:05
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 3259aa5 to 38a7565 Compare August 10, 2022 18:07
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 38a7565 to 8e0d478 Compare September 25, 2022 20:51
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 8e0d478 to ff7fd15 Compare November 20, 2022 15:42
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from ff7fd15 to cde5148 Compare March 16, 2023 13:55
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from cde5148 to e7c73d2 Compare April 17, 2023 10:41
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from e7c73d2 to 60fcd6c Compare May 28, 2023 11:50
@renovate renovate bot changed the title Update dependency graphql-tools to v8 Update dependency graphql-tools to v9 May 28, 2023
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 60fcd6c to b7bcb07 Compare February 23, 2024 15:35
@iquabius iquabius closed this Mar 14, 2024
Copy link
Contributor Author

renovate bot commented Mar 14, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/major-graphql-tools-monorepo branch March 14, 2024 21:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant