chore(deps): update graphqlcodegenerator monorepo #12
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/graphqlcodegenerator-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^2.11.6
->^5.0.0
^2.3.3
->^5.0.0
^2.7.3
->^4.0.0
^2.5.3
->^4.0.0
^3.3.3
->^4.0.0
^4.0.1
->^6.0.0
Release Notes
dotansimha/graphql-code-generator (@graphql-codegen/cli)
v5.0.3
Compare Source
Patch Changes
#10069
8bb34e7
Thanks @renovate! - dependencies updates:@whatwg-node/fetch@^0.9.20
↗︎ (from^0.8.0
, independencies
)graphql-config@^5.1.1
↗︎ (from^5.0.2
, independencies
)e0092b5
Thanks @ardatan! - Bump whatwg-node and graphql-configUpdated dependencies [
8471a18
,67e7556
]:v5.0.2
Compare Source
Patch Changes
#9813
4e69568
Thanks @saihaj! - bumping for a releaseUpdated dependencies [
4e69568
]:v5.0.1
Compare Source
Patch Changes
#9811
d8364e045
Thanks @saihaj! - dependencies updates:@graphql-codegen/client-preset@^4.1.0
↗︎ (todependencies
)#9811
d8364e045
Thanks @saihaj! - ignore events in.git
directory#9811
d8364e045
Thanks @saihaj! - Surface error occurring during import of @parcel/watcher#9811
d8364e045
Thanks @saihaj! - Include @graphql-codegen/client-preset in @graphql-codegen/cli by default#9811
d8364e045
Thanks @saihaj! - fix watcher unable to find highest common directory on WindowsUpdated dependencies [
d8364e045
,d8364e045
,d8364e045
,d8364e045
]:v5.0.0
Compare Source
Major Changes
dd9c7e148
Thanks @valkum! - Make @parcel/watcher optionalPatch Changes
#9513
fdd19d24d
Thanks @cichelero! - Update yaml dependency to 2.3.1Updated dependencies [
bb1e0e96e
]:v4.0.1
Compare Source
Patch Changes
#9479
0aa444b5d
Thanks @gilgardosh! - dependencies updates:graphql-config@^5.0.2
↗︎ (from^5.0.1
, independencies
)#9479
0aa444b5d
Thanks @gilgardosh! - Update graphql-config to v^5.0.2v4.0.0
Compare Source
Major Changes
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Patch Changes
#9449
4d9ea1a5a
Thanks @n1ru4l! - dependencies updates:graphql-config@^5.0.0
↗︎ (from^4.5.0
, independencies
)#9449
4d9ea1a5a
Thanks @n1ru4l! - dependencies updates:@graphql-tools/apollo-engine-loader@^8.0.0
↗︎ (from^7.3.6
, independencies
)@graphql-tools/code-file-loader@^8.0.0
↗︎ (from^7.3.17
, independencies
)@graphql-tools/git-loader@^8.0.0
↗︎ (from^7.2.13
, independencies
)@graphql-tools/github-loader@^8.0.0
↗︎ (from^7.3.28
, independencies
)@graphql-tools/graphql-file-loader@^8.0.0
↗︎ (from^7.5.0
, independencies
)@graphql-tools/json-file-loader@^8.0.0
↗︎ (from^7.4.1
, independencies
)@graphql-tools/load@^8.0.0
↗︎ (from^7.8.0
, independencies
)@graphql-tools/prisma-loader@^8.0.0
↗︎ (from^7.2.69
, independencies
)@graphql-tools/url-loader@^8.0.0
↗︎ (from^7.17.17
, independencies
)@graphql-tools/utils@^10.0.0
↗︎ (from^9.0.0
, independencies
)cosmiconfig@^8.1.3
↗︎ (from^7.0.0
, independencies
)graphql-config@^5.0.1
↗︎ (from^4.5.0
, independencies
)#9371
d431f426e
Thanks @Axxxx0n! - Fixed option ignoreNoDocuments when using graphql configs#9275
2a5da5894
Thanks @milesrichardson! - Trigger rebuilds in watch mode while respecting rules of precedence and negation, both in terms of global (top-level) config vs. local (per-output target) config, and in terms of watch patterns (higher priority) vs. documents/schemas (lower priority). This fixes an issue with overly-aggressive rebuilds during watch mode.Updated dependencies [
4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,63827fabe
,bb66c2a31
]:v3.3.1
Compare Source
Patch Changes
#9267
183749346
Thanks @milesrichardson! - Fix watch mode to listen to longest common directory prefix of relevant files, rather than only files below the current working directory (fixes #9266).#9280
ca1d72c40
Thanks @saihaj! - fix the default output directory for init commandv3.3.0
Compare Source
Minor Changes
#9151
b7dacb21f
Thanks @'./user/schema.mappers#UserMapper',! - AddwatchPattern
config option forgenerates
sections.By default,
watch
mode automatically watches all GraphQL schema and document files. This means when a change is detected, Codegen CLI is run.A user may want to run Codegen CLI when non-schema and non-document files are changed. Each
generates
section now has awatchPattern
option to allow more file patterns to be added to the list of patterns to watch.In the example below, mappers are exported from
schema.mappers.ts
files. We want to re-run Codegen if the content of*.mappers.ts
files change because they change the generated types file. To solve this, we can add mapper file patterns to watch using the glob pattern used for schema and document files.Then, run Codegen CLI in
watch
mode:Now, updating
*.mappers.ts
files re-runs Codegen! 🎉Note:
watchPattern
is only used inwatch
mode i.e. running CLI with--watch
flag.Patch Changes
b7dacb21f
,f104619ac
]:v3.2.2
Compare Source
Patch Changes
#9086
a34cef35b
Thanks @beerose! - dependencies updates:graphql-config@^4.5.0
↗︎ (from^4.4.0
, independencies
)jiti@^1.17.1
↗︎ (todependencies
)cosmiconfig-typescript-loader@^4.3.0
↗︎ (fromdependencies
)ts-node@^10.9.1
↗︎ (fromdependencies
)#9086
a34cef35b
Thanks @beerose! - Supportcodegen.ts
in ESM projectsv3.2.1
Compare Source
Patch Changes
#9051
f7313f7ca
Thanks @saihaj! - dependencies updates:micromatch@^4.0.5
↗︎ (todependencies
)#9051
f7313f7ca
Thanks @saihaj! - only run generate for files that users have listed in config to avoid running this over every change that codegen is not supposed to executev3.2.0
Compare Source
Minor Changes
288ed0977
Thanks @saihaj! - use @parcel/watcher for improved watch functionalityPatch Changes
288ed0977
Thanks @saihaj! - dependencies updates:@parcel/watcher@^2.1.0
↗︎ (todependencies
)chokidar@^3.5.2
↗︎ (fromdependencies
)v3.1.0
Compare Source
Minor Changes
#8893
a118c307a
Thanks @n1ru4l! - It is no longer mandatory to declare an empty plugins array when using a preset#8723
a3309e63e
Thanks @kazekyo! - Introduce a new feature called DocumentTransform.DocumentTransform is a functionality that allows you to modify
documents
before they are processed by plugins. You can use functions passed to thedocumentTransforms
option to make changes to GraphQL documents.To use this feature, you can write
documentTransforms
as follows:For instance, to remove a
@localOnlyDirective
directive fromdocuments
, you can write the following code:DocumentTransform can also be specified by file name. You can create a custom file for a specific transformation and pass it to
documentTransforms
.Let's create the document transform as a file:
Then, you can specify the file name as follows:
Patch Changes
4c422ccf6
Thanks @renovate! - dependencies updates:@whatwg-node/fetch@^0.8.0
↗︎ (from^0.6.0
, independencies
)8206b268d
,8206b268d
,a118c307a
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
#8883
321d5112e
Thanks @Solo-steven! - Fix PluckConfig overwrite problem.Updated dependencies [
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator (@graphql-codegen/typed-document-node)
v5.0.12
Compare Source
Patch Changes
1617e3c
,fa64fbf
]:v5.0.11
Compare Source
Patch Changes
#10160
c7af639
Thanks @jyasskin! - Allow explicitundefined
in additional to optional argumentsUpdated dependencies [
55a1e9e
,a235051
]:v5.0.10
Compare Source
Patch Changes
3f4f546
]:v5.0.9
Compare Source
Patch Changes
79fee3c
]:v5.0.8
Compare Source
Patch Changes
808ada5
,14ce39e
]:v5.0.7
Compare Source
Patch Changes
dfc5310
,156cc2b
,dfc5310
,b49457b
]:v5.0.6
Compare Source
Patch Changes
920b443
,ed9c205
]:v5.0.5
Compare Source
Patch Changes
53f270a
]:v5.0.4
Compare Source
Patch Changes
#9813
4e69568
Thanks @saihaj! - bumping for a releaseUpdated dependencies [
4e69568
]:v5.0.3
Compare Source
Patch Changes
7718a8113
]:v5.0.2
Compare Source
Patch Changes
d8364e045
Thanks @saihaj! - dependencies updates:tslib@~2.6.0
↗︎ (from~2.5.0
, independencies
)d8364e045
,d8364e045
,d8364e045
,d8364e045
]:v5.0.1
Compare Source
Patch Changes
1617e3c
,fa64fbf
]:v5.0.0
Compare Source
Major Changes
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Minor Changes
#9196
3848a2b73
Thanks @beerose! - Add@defer
directive supportWhen a query includes a deferred fragment field, the server will return a partial response with the non-deferred fields first, followed by the remaining fields once they have been resolved.
Once start using the
@defer
directive in your queries, the generated code will automatically include support for the directive.The generated type for
GetUserQuery
will have information that the fragment is incremental, meaning it may not be available right away.Apart from generating code that includes support for the
@defer
directive, the Codegen also exports a utility function calledisFragmentReady
. You can use it to conditionally render components based on whether the data for a deferredfragment is available:
Patch Changes
4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,3848a2b73
,ba84a3a27
,63827fabe
,50471e651
,5aa95aa96
,ca02ad172
,e1dc75f3c
,bb66c2a31
,5950f5a68
,5aa95aa96
]:v4.0.1
Compare Source
Patch Changes
386cf9044
,402cb8ac0
]:v4.0.0
Compare Source
Major Changes
2256c8b5d
Thanks @beerose! - AddTypedDocumentNode
string alternative that doesn't require GraphQL AST on the client. This change requires@graphql-typed-document-node/core
in version3.2.0
or higher.Patch Changes
e56790104
,b7dacb21f
,f104619ac
,acb647e4e
,9f4d9c5a4
]:v3.0.2
Compare Source
Patch Changes
ba0610bbd
,4b49f6fbe
,b343626c9
]:v3.0.1
Compare Source
Patch Changes
#8879
8206b268d
Thanks @renovate! - dependencies updates:tslib@~2.5.0
↗︎ (from~2.4.0
, independencies
)#8971
6b6fe3cbc
Thanks @n1ru4l! - Allow passing fragment documents to APIs like ApollosreadFragment
Updated dependencies [
8206b268d
,8206b268d
,a118c307a
,6b6fe3cbc
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator (@graphql-codegen/typescript)
v4.1.2
Compare Source
Patch Changes
1617e3c
,fa64fbf
]:v4.1.1
Compare Source
Patch Changes
55a1e9e
,a235051
]:v4.1.0
Compare Source
Minor Changes
#10077
3f4f546
Thanks @eddeee888! - Extendconfig.avoidOptions
to support query, mutation and subscriptionPreviously,
config.avoidOptions.resolvers
was being used to make query, mutation and subscription fields non-optional.Now,
config.avoidOptions.query
,config.avoidOptions.mutation
andconfig.avoidOptions.subscription
can be used to target the respective types.Patch Changes
3f4f546
]:v4.0.9
Compare Source
Patch Changes
79fee3c
]:v4.0.8
Compare Source
Patch Changes
808ada5
,14ce39e
]:v4.0.7
Compare Source
Patch Changes
dfc5310
,156cc2b
,dfc5310
,b49457b
]:v4.0.6
Compare Source
Patch Changes
920b443
,ed9c205
]:v4.0.5
Compare Source
Patch Changes
53f270a
]:v4.0.4
Compare Source
Patch Changes
#9813
4e69568
Thanks @saihaj! - bumping for a releaseUpdated dependencies [
4e69568
]:v4.0.3
Compare Source
Patch Changes
7718a8113
]:v4.0.2
Compare Source
Patch Changes
d8364e045
Thanks @saihaj! - dependencies updates:tslib@~2.6.0
↗︎ (from~2.5.0
, independencies
)d8364e045
,d8364e045
,d8364e045
,d8364e045
,d8364e045
]:v4.0.1
Compare Source
Patch Changes
#9497
2276708d0
Thanks @eddeee888! - Revert default ID scalar input type to stringWe changed the ID Scalar input type from
string
tostring | number
in the latest major version oftypescript
plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends ontypescript
plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.Updated dependencies [
2276708d0
]:v4.0.0
Compare Source
Major Changes
#9375
ba84a3a27
Thanks @eddeee888! - Implement Scalars with input/output typesIn GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:
string
ornumber
in the inputstring
in its selection set (i.e output)string
in the resolver (GraphQL parsesstring
ornumber
received from the client tostring
)string
ornumber
(GraphQL serializes the value tostring
before sending it to the client )Currently, we represent every Scalar with only one type. This is what codegen generates as base type:
Then, this is used in both input and output type e.g.
This PR extends each Scalar to have input and output:
Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:
Note that for
typescript-resolvers
, the type of ID needs to be inverted. However, the referenced types in GraphQL input/output types should still work correctly:Config changes:
If correctly, wired up, the following will be generated:
BREAKING CHANGE: This changes Scalar types which could be referenced in other plugins. If you are a plugin maintainer and reference Scalar, please update your plugin to use the correct input/output types.
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Minor Changes
#9196
3848a2b73
Thanks @beerose! - Add@defer
directive supportWhen a query includes a deferred fragment field, the server will return a partial response with the non-deferred fields first, followed by the remaining fields once they have been resolved.
Once start using the
@defer
directive in your queries, the generated code will automatically include support for the directive.The generated type for
GetUserQuery
will have information that the fragment is incremental, meaning it may not be available right away.Apart from generating code that includes support for the
@defer
directive, the Codegen also exports a utility function calledisFragmentReady
. You can use it to conditionally render components based on whether the data for a deferredfragment is available:
#9304
e1dc75f3c
Thanks @esfomeado! - Added support for disabling suffixes on Enums.Patch Changes
4d9ea1a5a
,4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,3848a2b73
,ba84a3a27
,63827fabe
,50471e651
,5aa95aa96
,ca02ad172
,e1dc75f3c
,bb66c2a31
,5950f5a68
,5aa95aa96
]:v3.0.4
Compare Source
Patch Changes
386cf9044
,402cb8ac0
]:v3.0.3
Compare Source
Patch Changes
#9150
92d86b009
Thanks @rliljest! - Properly escape enum identifiers when enumsAsConst is usedUpdated dependencies [
e56790104
,b7dacb21f
,f104619ac
,acb647e4e
,9f4d9c5a4
]:v3.0.2
Compare Source
Patch Changes
ba0610bbd
,4b49f6fbe
,b343626c9
]:v3.0.1
Compare Source
Patch Changes
8206b268d
Thanks @renovate! - dependencies updates:tslib@~2.5.0
↗︎ (from~2.4.0
, independencies
)8206b268d
,8206b268d
,8206b268d
,a118c307a
,6b6fe3cbc
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)
v4.4.0
Compare Source
Minor Changes
fa64fbf
Thanks @jerelmiller! - Add support for Apollo Client@unmask
directive with fragment masking.Patch Changes
1617e3c
,fa64fbf
]:v4.3.1
Compare Source
Patch Changes
55a1e9e
,a235051
]:v4.3.0
Compare Source
Minor Changes
#10077
3f4f546
Thanks @eddeee888! - Extendconfig.avoidOptions
to support query, mutation and subscriptionPreviously,
config.avoidOptions.resolvers
was being used to make query, mutation and subscription fields non-optional.Now,
config.avoidOptions.query
,config.avoidOptions.mutation
andconfig.avoidOptions.subscription
can be used to target the respective types.Patch Changes
3f4f546
]:v4.2.3
Compare Source
Patch Changes
79fee3c
]:v4.2.2
Compare Source
Patch Changes
808ada5
,14ce39e
]:v4.2.1
Compare Source
Patch Changes
dfc5310
,156cc2b
,dfc5310
,b49457b
]:v4.2.0
Compare Source
Minor Changes
920b443
Thanks @gmurphey! - Added allowUndefinedQueryVariables as config optionPatch Changes
#9842
ed9c205
Thanks @henryqdineen! - properly handle aliased conditionalsUpdated dependencies [
920b443
,ed9c205
]:v4.1.3
Compare Source
Patch Changes
53f270a
]:v4.1.2
Compare Source
Patch Changes
#9813
4e69568
Thanks @saihaj! - bumping for a releaseUpdated dependencies [
4e69568
]:v4.1.1
Compare Source
Patch Changes
7718a8113
]:v4.1.0
Compare Source
Minor Changes
d8364e045
Thanks @saihaj! - fix: out-of-memory crash (fixes #7720)perf: implement a caching mechanism that makes sure the type originating at the same location is never generated twice, as long as the combination of selected fields and possible types matches
feat: implement
extractAllFieldsToTypes: boolean
feat: implement
printFieldsOnNewLines: boolean
Patch Changes
d8364e045
Thanks @saihaj! - dependencies updates:tslib@~2.6.0
↗︎ (from~2.5.0
, independencies
)d8364e045
,d8364e045
,d8364e045
,d8364e045
,d8364e045
]:v4.0.1
Compare Source
Patch Changes
#9497
2276708d0
Thanks @eddeee888! - Revert default ID scalar input type to stringWe changed the ID Scalar input type from
string
tostring | number
in the latest major version oftypescript
plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends ontypescript
plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.Updated dependencies [
2276708d0
]:v4.0.0
Compare Source
Major Changes
#9375
ba84a3a27
Thanks @eddeee888! - Implement Scalars with input/output typesIn GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:
string
ornumber
in the inputstring
in its selection set (i.e output)string
in the resolver (GraphQL parsesstring
ornumber
received from the client tostring
)string
ornumber
(GraphQL serializes the value tostring
before sending it to the client )Currently, we represent every Scalar with only one type. This is what codegen generates as base type:
Then, this is used in both input and output type e.g.
This PR extends each Scalar to have input and output:
Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:
Note that for
typescript-resolvers
, the type of ID needs to be inverted. However, the referenced types in GraphQL input/output types should still work correctly:Config changes:
If correctly, wired up, the following will be generated:
BREAKING CHANGE: This changes Scalar types which could be referenced in other plugins. If you are a plugin maintainer and reference Scalar, please update your plugin to use the correct input/output types.
bb66c2a31
Thanks @n1ru4l! - Require Node.js>= 16
. Drop support for Node.js 14Minor Changes
#9196
3848a2b73
Thanks @beerose! - Add@defer
directive supportWhen a query includes a deferred fragment field, the server will return a partial response with the non-deferred fields first, followed by the remaining fields once they have been resolved.
Once start using the
@defer
directive in your queries, the generated code will automatically include support for the directive.The generated type for
GetUserQuery
will have information that the fragment is incremental, meaning it may not be available right away.Apart from generating code that includes support for the
@defer
directive, the Codegen also exports a utility function calledisFragmentReady
. You can use it to conditionally render components based on whether the data for a deferredfragment is available:
#9304
e1dc75f3c
Thanks @esfomeado! - Added support for disabling suffixes on Enums.Patch Changes
4d9ea1a5a
,4d9ea1a5a
,f46803a8c
,3848a2b73
,ba84a3a27
,63827fabe
,50471e651
,5aa95aa96
,ca02ad172
,e1dc75f3c
,bb66c2a31
,5950f5a68
,5aa95aa96
]:v3.0.4
Compare Source
Patch Changes
386cf9044
,402cb8ac0
]:v3.0.3
Compare Source
Patch Changes
e56790104
,b7dacb21f
,f104619ac
,92d86b009
,acb647e4e
,9f4d9c5a4
]:v3.0.2
Compare Source
Patch Changes
ba0610bbd
,4b49f6fbe
,b343626c9
]:v3.0.1
Compare Source
Patch Changes
8206b268d
Thanks @renovate! - dependencies updates:tslib@~2.5.0
↗︎ (from~2.4.0
, independencies
)8206b268d
,8206b268d
,8206b268d
,a118c307a
,6b6fe3cbc
,a3309e63e
]:v3.0.0
Compare Source
Major Changes
fd0b0c813
Thanks @n1ru4l! - drop Node.js 12 supportPatch Changes
fc79b65d4
,fd0b0c813
]:dotansimha/graphql-code-generator-community (@graphql-codegen/typescript-react-apollo)
v4.3.2
Compare Source
Patch Changes
ea83cf4
Thanks @jefrydco! - feat: support skip token for useSuspenseQuery
v4.3.1
Compare Source
Patch Changes
7df8028
Thanks @scottopherson! - Move
graphql-tag
todevDependencies
frompeerDependencies
.v4.3.0
Compare Source
Minor Changes
3e2c8de
Thanks @tomaskukk! - Improved type-safety: when a query contains
required variables, passing the variables object to the useQuery hook is enforced
v4.2.0
Compare Source
Minor Changes
ba7e551
Thanks @rickdunkin! - Apollo Client
useFragment
hookPatch Changes
fa53f8f
Thanks @namoscato! - fix: loosen defaultBaseOptions type
v4.1.0
Compare Source
Minor Changes
d86d2052a
Thanks @Hal-ang! - feat: support useSuspenseQuery
v4.0.0
Compare Source
Major Changes
218778010
Thanks @saihaj! - Drop support for Node.js 12 and 14. Require Node.js
>= 16
Patch Changes
ef0adf8c2
Thanks @renovate! - dependencies updates:
tslib@~2.6.0
↗︎ (from~2.4.0
, independencies
)dotansimha/graphql-code-generator-community (@graphql-codegen/typescript-react-query)
v6.1.0
Compare Source
Minor Changes
b403529
Thanks @neil585456525! - Fix importOperationTypesFrom missing
prefix
v6.0.0
Compare Source
Major Changes
935b51f07
Thanks @neil585456525! - Support react-query v5
Minor Changes
df7683e95
Thanks @saihaj! - Allow fetcher config to accept both
string
andobject
.object
let's user specify the import path to theirGraphQLClient
instance. So itwill make it easier to generated hooks by not passing down GraphQLClient.
v5.0.0
Compare Source
Major Changes
#324
d6f48354b
Thanks @giubatt! - removed unused pageParamKey parameter from
infinite queries hook call
#411
218778010
Thanks @saihaj! - Drop support for Node.js 12 and 14. Require Node.js
>= 16
Minor Changes
218778010
Thanks @saihaj! - add exposeQueryRootKeys
Patch Changes
#422
ef0adf8c2
Thanks @renovate! - dependencies updates:
tslib@~2.6.0
↗︎ (from~2.4.0
, independencies
)#411
218778010
Thanks @saihaj! - Provide reactQueryImportFrom field to custom
react-query import from
#391
14dcc7603
Thanks @AlanSl! - Correct default value in legacyMode docs comment
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 Renovate Bot.
010e582b86
to8451307abb
8451307abb
to27fc69f7eb
27fc69f7eb
tof1b2408351
f1b2408351
to63b59c652c
63b59c652c
tocdd7b4429c
cdd7b4429c
to6c2fb9134f
6c2fb9134f
toce1e62d6ae
ce1e62d6ae
to39ee1373ad
39ee1373ad
to573d8fc09f
573d8fc09f
to3f1aa06adc
3f1aa06adc
to7f5e7c27fd
7f5e7c27fd
to4f4a082edb
4f4a082edb
to1d5d01eff5
chore(deps): update graphqlcodegenerator monorepo to v3to chore(deps): update graphqlcodegenerator monorepo1d5d01eff5
to8ec8b68523
8ec8b68523
toce263f9228
ce263f9228
to702b51f32c
702b51f32c
todd1aef9c95
Checkout
From your project repository, check out a new branch and test the changes.