fix(deps): update graphql-tools monorepo - autoclosed #63
+261
−92
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
71ff18c to
fc4bb56
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
4 times, most recently
from
4ac07a7 to
bafcd1b
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
bafcd1b to
efa0fa8
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
0124c0b to
1af379d
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
318079a to
93f14f8
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
def984e to
ee4f4bf
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
ed331ec to
16c8100
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
16c8100 to
f7719ff
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
f7719ff to
0179158
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
0179158 to
9854add
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
9854add to
e0efc62
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
e0efc62 to
b48e566
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
2 times, most recently
from
0e4dfe5 to
fa9c587
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
fa9c587 to
273eac8
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^7.1.0->7.5.5^7.3.1->7.7.7^8.1.2->8.3.6^8.2.0->8.5.1^8.2.2->8.12.0Release Notes
ardatan/graphql-tools (@graphql-tools/graphql-file-loader)
v7.5.5Compare Source
Patch Changes
43c736bd]:v7.5.4Compare Source
Patch Changes
71cb4fae,403ed450]:v7.5.3Compare Source
Patch Changes
4fe3d9c0]:v7.5.2Compare Source
Patch Changes
2609d71f]:v7.5.1Compare Source
Patch Changes
#4624
e3167edcThanks @n1ru4l! - Fix CommonJS TypeScript resolution withmoduleResolutionnode16ornodenextUpdated dependencies [
e3167edc]:v7.5.0Compare Source
Minor Changes
2a3b45e: Allow&in filenames.Related to https://github.com/dotansimha/graphql-code-generator/issues/6174
Patch Changes
2a3b45e]v7.4.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v7.3.16Compare Source
Patch Changes
4914970]v7.3.15Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v7.3.14Compare Source
Patch Changes
a538635]da7ad43]v7.3.13Compare Source
Patch Changes
c0762ee]v7.3.12Compare Source
Patch Changes
0fc510c]v7.3.11Compare Source
Patch Changes
31a33e2]v7.3.10Compare Source
Patch Changes
cb23887]v7.3.9Compare Source
Patch Changes
0bbb176]v7.3.8Compare Source
Patch Changes
904c084]v7.3.7Compare Source
Patch Changes
be2c02d]v7.3.6Compare Source
Patch Changes
d36d530]v7.3.5Compare Source
Patch Changes
0c0c685: fix - align versionsv7.3.4Compare Source
Patch Changes
1834136: feat(visitResult): ignore if field not present in visited object1834136]v7.3.3Compare Source
Patch Changes
3173a69: fix(graphql/json-loader): raise error if one of the found files failsv7.3.2Patch Changes
4bfb342: enhance: use ^ for tslib dependency4bfb342]v7.3.1Patch Changes
4914970]v7.3.0Minor Changes
94bee8b: This change allows pkg - npm to have snapshot stored schema files read by graphql-tools.pkg generates cross platform binary executables of node apps and includes a packaged read-only filesystem called a snapshot.
This change was made because the pkg snapshot file system does not support use of globbing.
If you want to use the snapshot facilty with pkg for schema files then:
v7.2.0Minor Changes
00d06c2: feat(loader): providenoSilentErrorsoption to allow raising errors during loader resolutionPatch Changes
1e90f09]ardatan/graphql-tools (@graphql-tools/load)
v7.7.7Compare Source
Patch Changes
43c736bd]:v7.7.6Compare Source
Patch Changes
71cb4fae,403ed450]:v7.7.5Compare Source
Patch Changes
4fe3d9c0]:v7.7.4Compare Source
Patch Changes
2609d71f]:v7.7.3Compare Source
Patch Changes
821ef03cThanks @ardatan! - Fix import for ESM supportv7.7.2Compare Source
Patch Changes
#4624
e3167edcThanks @n1ru4l! - Fix CommonJS TypeScript resolution withmoduleResolutionnode16ornodenextUpdated dependencies [
8cc8721f,e3167edc]:v7.7.1Compare Source
Patch Changes
2a3b45e]v7.7.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v7.6.0Compare Source
Minor Changes
4914970:mergeSchemaswas skippingdefaultFieldResolveranddefaultMergedResolverby default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So newincludeDefaultMergedResolverflag is introduced ingetResolversFromSchemato put default "proxy" resolvers in the extracted resolver map formergeSchemas.This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing
defaultMergedResolverin the final merged schema which should come from the wrapped schema.Patch Changes
4914970: No longer callmergeSchemasif a single schema is loaded.Previously all typeDefs and resolvers were extracted and the schema was rebuilt from scratch.
But this is not necessary if there is only one schema loaded with
loadSchema4914970]v7.5.14Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v7.5.13Compare Source
Patch Changes
da7ad43]v7.5.12Compare Source
Patch Changes
c0762ee]v7.5.11Compare Source
Patch Changes
0fc510c]v7.5.10Compare Source
Patch Changes
31a33e2]v7.5.9Compare Source
Patch Changes
cb23887]v7.5.8Compare Source
Patch Changes
0bbb176]v7.5.7Compare Source
Patch Changes
904c084]v7.5.6Compare Source
Patch Changes
722abad]v7.5.5Compare Source
Patch Changes
be2c02d]v7.5.4Compare Source
Patch Changes
d36d530]v7.5.3Compare Source
Patch Changes
0c0c685: fix - align versions0c0c685]v7.5.2Compare Source
Patch Changes
1834136: feat(visitResult): ignore if field not present in visited object1834136]v7.5.1Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v7.5.0Compare Source
Minor Changes
b107413: feat(load): support custom require for custom loadersPatch Changes
7b5d72c]v7.4.1Compare Source
Patch Changes
4bfb342: enhance: use ^ for tslib dependency4bfb342]v7.4.0Compare Source
Minor Changes
149afdd: fix: getting ready for GraphQL v16Patch Changes
149afdd]v7.3.2Compare Source
Patch Changes
8079d43: Fix loadSchema no longer accepting options.schemasardatan/graphql-tools (@graphql-tools/merge)
v8.3.6Compare Source
Patch Changes
43c736bd]:v8.3.5Compare Source
Patch Changes
71cb4fae,403ed450]:v8.3.4Compare Source
Patch Changes
4fe3d9c0]:v8.3.3Compare Source
Patch Changes
#4643
2609d71fThanks @ardatan! - Revert the breaking change introduced in@graphql-tools/mergeUpdated dependencies [
2609d71f]:v8.3.2Compare Source
Patch Changes
#4624
e3167edcThanks @n1ru4l! - Fix CommonJS TypeScript resolution withmoduleResolutionnode16ornodenextUpdated dependencies [
e3167edc]:v8.3.1Compare Source
Patch Changes
2a3b45e]v8.3.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v8.2.15Compare Source
Patch Changes
4914970]v8.2.14Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.2.13Compare Source
Patch Changes
da7ad43]v8.2.12Compare Source
Patch Changes
c0762ee]v8.2.11Compare Source
Patch Changes
0fc510c]v8.2.10Compare Source
Patch Changes
31a33e2]v8.2.9Compare Source
Patch Changes
cb23887]v8.2.8Compare Source
Patch Changes
0bbb176]v8.2.7Compare Source
Patch Changes
904c084]v8.2.6Compare Source
Patch Changes
be2c02d]v8.2.5Compare Source
Patch Changes
d36d530]v8.2.4Compare Source
Patch Changes
0c0c685: fix - align versionsv8.2.3Compare Source
Patch Changes
1834136: feat(visitResult): ignore if field not present in visited object1834136]v8.2.2Compare Source
Patch Changes
1269140: UpdatemergeTypeDefsto mergeimplementsdefinitions defined within interface extensions.v8.2.1Compare Source
Patch Changes
4914970]v8.2.0Compare Source
Minor Changes
149afdd: fix: getting ready for GraphQL v16Patch Changes
149afdd]ardatan/graphql-tools (@graphql-tools/schema)
v8.5.1Compare Source
Patch Changes
2a3b45e]v8.5.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v8.4.0Compare Source
Minor Changes
4914970:mergeSchemaswas skippingdefaultFieldResolveranddefaultMergedResolverby default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So newincludeDefaultMergedResolverflag is introduced ingetResolversFromSchemato put default "proxy" resolvers in the extracted resolver map formergeSchemas.This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing
defaultMergedResolverin the final merged schema which should come from the wrapped schema.Patch Changes
4914970]v8.3.14Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.3.13Compare Source
Patch Changes
da7ad43]v8.3.12Compare Source
Patch Changes
c0762ee]v8.3.11Compare Source
Patch Changes
0fc510c]v8.3.10Compare Source
Patch Changes
31a33e2]v8.3.9Compare Source
Patch Changes
cb23887]v8.3.8Compare Source
Patch Changes
0bbb176]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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.