Update graphqlcodegenerator monorepo (major) #60

renovate · 2023-05-24T09:41:14Z

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-codegen/cli (source)	`3.3.1` -> `6.0.1`
@graphql-codegen/typescript (source)	`3.0.4` -> `5.0.2`
@graphql-codegen/typescript-operations (source)	`3.0.4` -> `5.0.2`
@graphql-codegen/typescript-vue-urql (source)	`2.3.6` -> `3.2.1`
@graphql-codegen/urql-introspection (source)	`2.2.1` -> `3.0.1`

Release Notes

dotansimha/graphql-code-generator (@graphql-codegen/cli)

`v6.0.1`

Compare Source

Patch Changes

#10468 cb1b9d9 Thanks @eddeee888! - In watch mode, do not write output on failure

Previously, on partial or full failure, watch mode still write to output. However, since the output'd be an empty array, it will then call removeStaleFiles internally to remove all previously generated files.

This patch puts a temporary fix to avoid writing output on any failure to fix the described behaviour.

This also means the config.allowPartialOutputs does not work in watch mode for now.

`v6.0.0`

Compare Source

Major Changes

#10218 140298a Thanks @eddeee888! - Drop @graphql-tools/prisma-loader
#10218 140298a Thanks @eddeee888! - Add allowPartialOutputs flag to partially write successful generation to files
#10218 140298a Thanks @eddeee888! - Migrate inquirer to @inquirer/prompts
#10218 140298a Thanks @eddeee888! - Bump dependencies major versions:
- cosmiconfig v9
- debounce v2
- jiti v2.3
#10218 140298a Thanks @eddeee888! - Bump listr2 to v9
#10218 140298a Thanks @eddeee888! - Drop Node 18 support

Patch Changes

Updated dependencies [140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a]:
- @graphql-codegen/plugin-helpers@6.0.0
- @graphql-codegen/client-preset@5.0.0
- @graphql-codegen/core@5.0.0

`v5.0.7`

Compare Source

Patch Changes

#10150 e324382 Thanks @ArminWiebigke! - Allow functions to be passed as valid values for UrlSchemaOptions.customFetch. This was already possible, but the type definitions did not reflect that correctly.
#10358 157c823 Thanks @eddeee888! - Remove extraneous error stacktrace if fails to load @parcel/watcher
Updated dependencies [e324382, 98392fc]:
- @graphql-codegen/plugin-helpers@5.1.1
- @graphql-codegen/client-preset@4.8.2

`v5.0.6`

Compare Source

Patch Changes

#10338 5d1c4e1 Thanks @eddeee888! - Fix ignoreNoDocuments=true swallowing all errors
#10333 10ab58d Thanks @eddeee888! - Improve syntax error messages whilst loading schema/document
Updated dependencies [c5efba3]:
- @graphql-codegen/client-preset@4.8.1

`v5.0.5`

Compare Source

Patch Changes

#10282 7d7760d Thanks @oprypkhantc! - Fix watcher watching project root when schema URL is used

`v5.0.4`

Compare Source

Patch Changes

#10248 72eb86f Thanks @renovate! - dependencies updates:
- Updated dependency @whatwg-node/fetch@^0.10.0 ↗︎ (from ^0.9.20, in dependencies)
#10227 6f1741a Thanks @eddeee888! - Fix schema pointers type to allow an array of pointers
Updated dependencies [8737dd8, ed71811]:
- @graphql-codegen/client-preset@4.6.0

`v5.0.3`

Compare Source

Patch Changes

#10069 8bb34e7 Thanks @renovate! - dependencies updates:
- Updated dependency @whatwg-node/fetch@^0.9.20 ↗︎ (from ^0.8.0, in dependencies)
- Updated dependency graphql-config@^5.1.1 ↗︎ (from ^5.0.2, in dependencies)
e0092b5 Thanks @ardatan! - Bump whatwg-node and graphql-config
Updated dependencies [8471a18, 67e7556]:
- @graphql-codegen/client-preset@4.4.0

Patch Changes

#9513 fdd19d24d Thanks @cichelero! - Update yaml dependency to 2.3.1
Updated dependencies [bb1e0e96e]:
- @graphql-codegen/plugin-helpers@5.0.1

`v4.0.1`

Compare Source

Patch Changes

#9479 0aa444b5d Thanks @gilgardosh! - dependencies updates:
- Updated dependency graphql-config@^5.0.2 ↗︎ (from ^5.0.1, in dependencies)
#9479 0aa444b5d Thanks @gilgardosh! - Update graphql-config to v^5.0.2

`v4.0.0`

Compare Source

Major Changes

bb66c2a31 Thanks @n1ru4l! - Require Node.js >= 16. Drop support for Node.js 14

Patch Changes

#9449 4d9ea1a5a Thanks @n1ru4l! - dependencies updates:
- Updated dependency graphql-config@^5.0.0 ↗︎ (from ^4.5.0, in dependencies)
#9449 4d9ea1a5a Thanks @n1ru4l! - dependencies updates:
- Updated dependency @graphql-tools/apollo-engine-loader@^8.0.0 ↗︎ (from ^7.3.6, in dependencies)
- Updated dependency @graphql-tools/code-file-loader@^8.0.0 ↗︎ (from ^7.3.17, in dependencies)
- Updated dependency @graphql-tools/git-loader@^8.0.0 ↗︎ (from ^7.2.13, in dependencies)
- Updated dependency @graphql-tools/github-loader@^8.0.0 ↗︎ (from ^7.3.28, in dependencies)
- Updated dependency @graphql-tools/graphql-file-loader@^8.0.0 ↗︎ (from ^7.5.0, in dependencies)
- Updated dependency @graphql-tools/json-file-loader@^8.0.0 ↗︎ (from ^7.4.1, in dependencies)
- Updated dependency @graphql-tools/load@^8.0.0 ↗︎ (from ^7.8.0, in dependencies)
- Updated dependency @graphql-tools/prisma-loader@^8.0.0 ↗︎ (from ^7.2.69, in dependencies)
- Updated dependency @graphql-tools/url-loader@^8.0.0 ↗︎ (from ^7.17.17, in dependencies)
- Updated dependency @graphql-tools/utils@^10.0.0 ↗︎ (from ^9.0.0, in dependencies)
- Updated dependency cosmiconfig@^8.1.3 ↗︎ (from ^7.0.0, in dependencies)
- Updated dependency graphql-config@^5.0.1 ↗︎ (from ^4.5.0, in dependencies)
#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]:
- @graphql-codegen/core@4.0.0
- @graphql-codegen/plugin-helpers@5.0.0

dotansimha/graphql-code-generator (@graphql-codegen/typescript)

`v5.0.2`

Compare Source

Patch Changes

Updated dependencies [8258f1f]:
- @graphql-codegen/visitor-plugin-common@6.1.0

`v5.0.1`

Compare Source

Patch Changes

Updated dependencies [accdab6]:
- @graphql-codegen/visitor-plugin-common@6.0.1

`v5.0.0`

Compare Source

Major Changes

#10218 140298a Thanks @eddeee888! - Remove NameNode override
#10218 140298a Thanks @eddeee888! - Drop Node 18 support

Patch Changes

Updated dependencies [140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a, 140298a]:
- @graphql-codegen/visitor-plugin-common@6.0.0
- @graphql-codegen/plugin-helpers@6.0.0
- @graphql-codegen/schema-ast@5.0.0

`v4.1.6`

Compare Source

Patch Changes

Updated dependencies [f6909d1]:
- @graphql-codegen/visitor-plugin-common@5.8.0

`v4.1.5`

Compare Source

Patch Changes

Updated dependencies [d8566c0]:
- @graphql-codegen/visitor-plugin-common@5.7.1

`v4.1.4`

Compare Source

Patch Changes

Updated dependencies [6d7c1d7]:
- @graphql-codegen/visitor-plugin-common@5.7.0

`v4.1.3`

Compare Source

Patch Changes

Updated dependencies [60dd72f]:
- @graphql-codegen/visitor-plugin-common@5.6.1

`v4.1.2`

Compare Source

Patch Changes

Updated dependencies [1617e3c, fa64fbf]:
- @graphql-codegen/visitor-plugin-common@5.6.0

`v4.1.1`

Compare Source

Patch Changes

Updated dependencies [55a1e9e, a235051]:
- @graphql-codegen/visitor-plugin-common@5.5.0
- @graphql-codegen/plugin-helpers@5.1.0

`v4.1.0`

Compare Source

Minor Changes

#10077 3f4f546 Thanks @eddeee888! - Extend config.avoidOptions to support query, mutation and subscription

Previously, config.avoidOptions.resolvers was being used to make query, mutation and subscription fields non-optional.
Now, config.avoidOptions.query, config.avoidOptions.mutation and config.avoidOptions.subscription can be used to target the respective types.

Patch Changes

Updated dependencies [3f4f546]:
- @graphql-codegen/visitor-plugin-common@5.4.0

`v4.0.9`

Compare Source

Patch Changes

Updated dependencies [79fee3c]:
- @graphql-codegen/visitor-plugin-common@5.3.1

`v4.0.8`

Compare Source

Patch Changes

Updated dependencies [808ada5, 14ce39e]:
- @graphql-codegen/visitor-plugin-common@5.3.0

`v4.0.7`

Compare Source

Patch Changes

Updated dependencies [dfc5310, 156cc2b, dfc5310, b49457b]:
- @graphql-codegen/plugin-helpers@5.0.4
- @graphql-codegen/visitor-plugin-common@5.2.0

`v4.0.6`

Compare Source

Patch Changes

Updated dependencies [920b443, ed9c205]:
- @graphql-codegen/visitor-plugin-common@5.1.0

`v4.0.5`

Compare Source

Patch Changes

Updated dependencies [53f270a]:
- @graphql-codegen/visitor-plugin-common@5.0.0

`v4.0.4`

Compare Source

Patch Changes

#9813 4e69568 Thanks @saihaj! - bumping for a release
Updated dependencies [4e69568]:
- @graphql-codegen/visitor-plugin-common@4.1.2
- @graphql-codegen/schema-ast@4.0.2
- @graphql-codegen/plugin-helpers@5.0.3

`v4.0.3`

Compare Source

Patch Changes

Updated dependencies [7718a8113]:
- @graphql-codegen/visitor-plugin-common@4.1.1

`v4.0.2`

Compare Source

Patch Changes

#9811 d8364e045 Thanks @saihaj! - dependencies updates:
- Updated dependency tslib@~2.6.0 ↗︎ (from ~2.5.0, in dependencies)
Updated dependencies [d8364e045, d8364e045, d8364e045, d8364e045, d8364e045]:
- @graphql-codegen/plugin-helpers@5.0.2
- @graphql-codegen/schema-ast@4.0.1
- @graphql-codegen/visitor-plugin-common@4.1.0

`v4.0.1`

Compare Source

Patch Changes

#9497 2276708d0 Thanks @eddeee888! - Revert default ID scalar input type to string

We changed the ID Scalar input type from string to string | number in the latest major version of typescript plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends on typescript plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.
Updated dependencies [2276708d0]:
- @graphql-codegen/visitor-plugin-common@4.0.1

`v4.0.0`

Compare Source

Major Changes

#9375 ba84a3a27 Thanks @eddeee888! - Implement Scalars with input/output types

In GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:

A client may send string or number in the input
A client receives string in its selection set (i.e output)
A server receives string in the resolver (GraphQL parses string or number received from the client to string)
A server may return string or number (GraphQL serializes the value to string before sending it to the client )

Currently, we represent every Scalar with only one type. This is what codegen generates as base type:

export type Scalars = {
  ID: string
}

Then, this is used in both input and output type e.g.

export type Book = {
  __typename?: 'Book'
  id: Scalars['ID'] // Output's ID can be `string` 👍
}

export type QueryBookArgs = {
  id: Scalars['ID'] // Input's ID can be `string` or `number`. However, the type is only `string` here 👎
}

This PR extends each Scalar to have input and output:

export type Scalars = {
  ID: {
    input: string | number
    output: string
  }
}

Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:

export type Book = {
  __typename?: 'Book'
  id: Scalars['ID']['output'] // Output's ID can be `string` 👍
}

export type QueryBookArgs = {
  id: Scalars['ID']['input'] // Input's ID can be `string` or `number` 👍
}

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:

export type Scalars = {
  ID: {
    input: string;
    output: string | number;
  }
}

export type Book = {
  __typename?: "Book";
  id: Scalars["ID"]['output']; // Resolvers can return `string` or `number` in ID fields 👍
};

export type QueryBookArgs = {
  id: Scalars["ID"]['input']; // Resolvers receive `string` in ID fields 👍
};

export type ResolversTypes = {
  ID: ID: ResolverTypeWrapper<Scalars['ID']['output']>; // Resolvers can return `string` or `number` in ID fields 👍
}

export type ResolversParentTypes = {
  ID: Scalars['ID']['output']; // Resolvers receive `string` or `number` from parents 👍
};

Config changes:

Scalars option can now take input/output types:

config: {
  scalars: {
    ID: {
      input: 'string',
      output: 'string | number'
    }
  }
}

If a string is given (instead of an object with input/output fields), it will be used as both input and output types:

config: {
  scalars: {
    ID: 'string' // This means `string` will be used for both ID's input and output types
  }
}

BREAKING CHANGE: External module Scalar types need to be an object with input/output fields

config: {
  scalars: {
    ID: './path/to/scalar-module'
  }
}

If correctly, wired up, the following will be generated:

// Previously, imported `ID` type can be a primitive type, now it must be an object with input/output fields
import { ID } from './path/to/scalar-module'

export type Scalars = {
  ID: { input: ID['input']; output: ID['output'] }
}

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 14

Minor Changes

#9196 3848a2b73 Thanks @beerose! - Add @defer directive support

When 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.

// src/index.tsx
import { graphql } from './gql'
const OrdersFragment = graphql(`
  fragment OrdersFragment on User {
    orders {
      id
      total
    }
  }
`)
const GetUserQuery = graphql(`
  query GetUser($id: ID!) {
    user(id: $id) {
      id
      name
      ...OrdersFragment @&#8203;defer
    }
  }
`)

The generated type for GetUserQuery will have information that the fragment is incremental, meaning it may not be available right away.

// gql/graphql.ts
export type GetUserQuery = { __typename?: 'Query'; id: string; name: string } & ({
  __typename?: 'Query'
} & {
  ' $fragmentRefs'?: { OrdersFragment: Incremental<OrdersFragment> }
})

Apart from generating code that includes support for the @defer directive, the Codegen also exports a utility function called isFragmentReady. You can use it to conditionally render components based on whether the data for a deferred
fragment is available:

const OrdersList = (props: { data: FragmentType<typeof OrdersFragment> }) => {
  const data = useFragment(OrdersFragment, props.data);
  return (
    // render orders list
  )
};

function App() {
  const { data } = useQuery(GetUserQuery);
  return (
    {data && (
      <>
        {isFragmentReady(GetUserQuery, OrdersFragment, data)
					&& <OrdersList data={data} />}
      </>
    )}
  );
}
export default App;

#9304 e1dc75f3c Thanks @esfomeado! - Added support for disabling suffixes on Enums.

Patch Changes

Updated dependencies [4d9ea1a5a, 4d9ea1a5a, 4d9ea1a5a, f46803a8c, 3848a2b73, ba84a3a27, 63827fabe, 50471e651, 5aa95aa96, ca02ad172, e1dc75f3c, bb66c2a31, 5950f5a68, 5aa95aa96]:
- @graphql-codegen/plugin-helpers@5.0.0
- @graphql-codegen/schema-ast@4.0.0
- @graphql-codegen/visitor-plugin-common@4.0.0

dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)

`v5.0.2`

Compare Source

Patch Changes

Updated dependencies [8258f1f]:
- @graphql-codegen/visitor-plugin-common@6.1.0
- @graphql-codegen/typescript@5.0.2

`v5.0.1`

Compare Source

Patch Changes

Updated dependencies [accdab6]:
- @graphql-codegen/visitor-plugin-common@6.0.1
- @graphql-codegen/typescript@5.0.1

`v5.0.0`

Compare Source

Major Changes

#10218 140298a Thanks @eddeee888! - BREAKING CHANGE: Use Record<PropertyKey, never> instead of {} for empty object type
#10218 140298a Thanks @eddeee888! - Drop Node 18 support

Patch Changes

Updated dependencies [[140298a](https://redirect.github.com/dotansimha/graphq

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.

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

This PR was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from ac85ef4 to d2f09ac Compare June 2, 2023 17:22

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 9f86c65 to 9555a61 Compare June 22, 2023 21:02

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from bf695f5 to a8c92cc Compare July 3, 2023 04:00

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 8cf325d to d75fbdb Compare July 17, 2023 04:12

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d75fbdb to 37c5942 Compare July 24, 2023 04:14

renovate bot changed the title ~~Update graphqlcodegenerator monorepo to v4 (major)~~ Update graphqlcodegenerator monorepo (major) Jul 25, 2023

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from a3327a8 to 7369b6f Compare July 31, 2023 03:39

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0aefbdb to 0cace5d Compare August 14, 2023 04:16

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from ee10a22 to fed8517 Compare August 21, 2023 03:48

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from df2151b to 81394db Compare September 25, 2023 22:21

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 81394db to 89e2ad1 Compare February 6, 2024 15:25

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 89b9a46 to 464e17c Compare February 25, 2024 19:01

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 464e17c to 8edf2f1 Compare March 8, 2024 19:40

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from aff19bf to 6f489a9 Compare May 21, 2024 00:54

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 6f489a9 to a07b640 Compare May 28, 2024 16:16

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a07b640 to 4684748 Compare June 12, 2024 18:23

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 2464162 to 8294157 Compare October 28, 2024 14:47

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 9da2e30 to bc2745f Compare November 22, 2024 22:15

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 8f41133 to 2ae50f3 Compare December 18, 2024 11:27

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from fa707e2 to 54fd3f1 Compare January 28, 2025 14:34

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from f8ced3c to 078a5aa Compare February 19, 2025 16:41

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from c537ae4 to 6cca35d Compare February 23, 2025 22:55

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 6cca35d to 779a62e Compare March 27, 2025 13:02

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 779a62e to 8af724f Compare May 6, 2025 16:50

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 8af724f to 528bc25 Compare May 26, 2025 14:30

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 528bc25 to 796febe Compare June 6, 2025 02:45

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 5e6c352 to a97b93b Compare August 13, 2025 15:03

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a97b93b to 683eb41 Compare August 19, 2025 18:02

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 683eb41 to 21517e2 Compare August 31, 2025 09:43

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from ae8dce1 to 81687e7 Compare September 25, 2025 16:00

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 8a1508b to 69d4abc Compare October 5, 2025 17:11

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 69d4abc to 8f1d26f Compare October 21, 2025 09:42

Update graphqlcodegenerator monorepo

c8e8b2a

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 8f1d26f to c8e8b2a Compare October 22, 2025 11:06

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update graphqlcodegenerator monorepo (major) #60

Update graphqlcodegenerator monorepo (major) #60

Uh oh!

renovate bot commented May 24, 2023 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Update graphqlcodegenerator monorepo (major) #60

Are you sure you want to change the base?

Update graphqlcodegenerator monorepo (major) #60

Uh oh!

Conversation

renovate bot commented May 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented May 24, 2023 •

edited

Loading