Skip to content

chore(deps): update graphqlcodegenerator monorepo - #54

Open
renovate[bot] wants to merge 1 commit into
mainfrom
develop/renovete-graphqlcodegenerator-monorepo
Open

chore(deps): update graphqlcodegenerator monorepo#54
renovate[bot] wants to merge 1 commit into
mainfrom
develop/renovete-graphqlcodegenerator-monorepo

Conversation

@renovate

@renovate renovate Bot commented Feb 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/cli (source) ^6.0.0^6.1.1 age confidence
@graphql-codegen/typescript (source) ^5.0.0^5.0.7 age confidence
@graphql-codegen/typescript-operations (source) ^5.0.0^5.1.0 age confidence

Release Notes

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

v6.3.1

Compare Source

Patch Changes
  • #​10737
    be85118
    Thanks @​eddeee888! - Fix issue where same SDL in different
    documents are ignored when handling documents vs externalDocuments

v6.3.0

Compare Source

Minor Changes
  • #​10659
    e65d303
    Thanks @​ikusakov2! - Add support for externalDocuments

    externalDocuments declares GraphQL documents that will be read but will not have type files
    generated for them. These documents are available to plugins for type resolution (e.g. fragment
    types), but no output files will be generated based on them. Accepts the same formats as
    documents.

    This config option is useful for monorepos where each project may want to generate types for its
    own documents, but some may need to read shared fragments from across projects.

Patch Changes

v6.2.1

Compare Source

Patch Changes
  • #​10618 e804925 Thanks @​PalmerTurley34! - Honor per-output preset importExtension and emitLegacyCommonJSImports config instead of always using the root config values.

v6.2.0

Compare Source

Minor Changes
Patch Changes

v6.1.3

Compare Source

Patch Changes

v6.1.2

Compare Source

Patch Changes
  • #​10590 e173e11 Thanks @​ya2s! - Fix GraphQL Config loading to forward nested extensions.codegen.config options
    when loading schemas/documents, matching codegen.ts behavior.
dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v5.0.10

Compare Source

Patch Changes

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

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

v5.1.0

Compare Source

Minor Changes
  • #​10659
    e65d303
    Thanks @​ikusakov2! - Add support for externalDocuments

    externalDocuments declares GraphQL documents that will be read but will not have type files
    generated for them. These documents are available to plugins for type resolution (e.g. fragment
    types), but no output files will be generated based on them. Accepts the same formats as
    documents.

    This config option is useful for monorepos where each project may want to generate types for its
    own documents, but some may need to read shared fragments from across projects.

Patch Changes

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

Patch Changes

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • "on monday"
  • 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
renovate Bot requested a review from corrupt952 February 22, 2026 17:55
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch from 241546f to 5bbba32 Compare February 25, 2026 12:12
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo to ^5.0.7 chore(deps): update graphqlcodegenerator monorepo Feb 25, 2026
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 2 times, most recently from b3fa164 to 49bffc3 Compare March 9, 2026 18:00
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch from 49bffc3 to 98f886e Compare March 13, 2026 15:35
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 3 times, most recently from 04dd438 to 0b93660 Compare April 1, 2026 20:00
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch from 0b93660 to 273aa38 Compare April 8, 2026 18:58
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 2 times, most recently from 63337b9 to 32f0c34 Compare April 21, 2026 22:09
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch from 32f0c34 to 5e20afa Compare May 4, 2026 00:16
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 2 times, most recently from 59a8c31 to 59e0003 Compare May 18, 2026 15:57
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 2 times, most recently from 93fc49e to 0ffe9de Compare June 1, 2026 16:39
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch from 0ffe9de to af8c4c3 Compare June 11, 2026 14:54
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 2 times, most recently from 10dec09 to a30fc14 Compare July 17, 2026 08:53
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch 2 times, most recently from ac3c920 to 06faf9e Compare July 24, 2026 20:39
@renovate
renovate Bot force-pushed the develop/renovete-graphqlcodegenerator-monorepo branch from 06faf9e to 1987855 Compare July 30, 2026 18:07
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.

0 participants