Skip to content

Update graphqlcodegenerator monorepo (major)#184

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

Update graphqlcodegenerator monorepo (major)#184
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 25, 2023 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/cli (source) ^5.0.0 → ^7.0.0 age confidence
@graphql-codegen/typescript (source) ^4.0.1 → ^6.0.0 age confidence
@graphql-codegen/typescript-graphql-request (source) ^5.0.0 → ^7.0.0 age confidence
@graphql-codegen/typescript-operations (source) ^4.0.1 → ^6.0.0 age confidence

Release Notes

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

v7.1.2

Compare Source

Patch Changes

v7.1.1

Compare Source

Patch Changes

v7.1.0

Compare Source

Minor Changes
Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Update deps to latest, some
    only support ESM

    Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
    means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
    ESM-only packages.

    If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
    issues when running Jest tests, try using Vitest.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Drop Node 20 support

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Set noSilentErrors: true
    by default

    When multiple files match documents pattern, and there are syntax errors in some but not others,
    then the operations with errors are not included in the loaded documents list by default
    (noSilentErrors: false). This is annoying for users as there is no feedback loop during
    development.

    noSilentErrors: true is used as the default for Codegen users to make the feedback loop faster.
    It can still overriden in Codegen Config if desired.

Patch Changes

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.

v6.1.1

Compare Source

Patch Changes

  • #​10569 8cb7d43 Thanks @​etr2460! - fix(graphql-codegen-cli): Don't hang when 0 CPUs are found

    Fixes generation when 0 CPUs are returned by os.cpus(), which occurs in sandbox environments.

v6.1.0

Compare Source

Minor Changes
Patch Changes

v6.0.2

Compare Source

Patch Changes

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
Patch Changes

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

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

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: visitors' config option are
    moved based on their use case

    • addTypename/skipTypename: is only a types-visitor concern. This is moved to types-visitor from
      base-visitor
    • nonOptionalTypename: is a documents-visitor and types-visitor concern. Moved from base-visitor
      there
    • extractAllFieldsToTypes: is a documents-visitor concern. Moved from base-visitor there
    • enumPrefix and enumSuffix: need to be in base-visitor as all 3 types of visitors need this to
      correctly sync the enum type names. This is moved to base visitor
    • ignoreEnumValuesFromSchema: is a documents-visitor and types-visitor concern. Moved from
      base-visitor there.
    • globalNamespace: is a documents-visitor concern. Moved from base-visitor there

    Refactors

    • documents-visitor no longer extends types-visitor option types as they have two distinct
      usages now. The types now extend base-visitor types. This is now consistent with
      documents-visitor extending base-visitor
    • Classes now handle config parsing and types at the same level e.g. if typescript-operations
      plugin parses configOne, then the types for configOne must be in that class, rather than in
      base-documents-visitor

    Note: These visitors are rolled up into one type for simplicity

    • base-visitor: includes base-visitor
    • documents-visitor: includes base-documents-visitor and typescript-operations visitor
    • types-visitor: includes base-types-visitor and typescript visitor
    • resolvers-visitor: includes base-resolvers-visitor and typescript-resolvers visitor

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: make unknown instead of
    any the default custom scalar type

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Update deps to latest, some
    only support ESM

    Node 20 support is dropped in this release. Node 22 comes with require() support for ESM, which
    means it's easier to integrate ES modules into applications. Therefore, it is safe to start using
    ESM-only packages.

    If you are a user, please upgrade to Node 22. If you are a lib maintainer and see ESM vs CJS
    issues when running Jest tests, try using Vitest.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Drop Node 20 support

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: typescript plugin no
    longer generates Exact utility type. Instead, typescript-operations generates said utility
    type for every file it creates. This is because it is used only for Variables, so we only need
    to generate it once for every generated operation file.

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: Remove unused utility types
    from typescript plugin as they were previously used for typescript-operations plugin:

    • MakeOptional
    • MakeMaybe
    • MakeEmpty
    • Incremental

    BREAKING CHANGE: Remove getRootTypeNames function because it's available in
    @graphql-utils/tools and not used anywhere

Minor Changes
  • #​10496
    afaace6
    Thanks @​eddeee888! - The typescript-operations plugin no longer
    generates InputMaybe and Scalars types; it now uses native Typescript types instead.
Patch Changes

v5.0.10

[Compare Source](https://redirect.

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 0e3ec9b to a9ffde6 Compare August 10, 2025 15:02
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a9ffde6 to 3164b8a Compare September 7, 2025 18:03
@renovate renovate Bot changed the title Update dependency @graphql-codegen/typescript-graphql-request to v6 Update graphqlcodegenerator monorepo (major) Sep 7, 2025
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0e9b642 to 377422e Compare September 29, 2025 17:25
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 377422e to b5a048f Compare October 5, 2025 17:54
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from b5a048f to d31b600 Compare October 21, 2025 21:48
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from b84d0b5 to c8d19fb Compare November 14, 2025 00:02
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from c8d19fb to 081522a Compare November 20, 2025 14:12
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from af8ee28 to 0f1a74f Compare December 3, 2025 20:09
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 0f1a74f to 1fe454a Compare December 18, 2025 14:32
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 2e72ed1 to a5df7f3 Compare January 11, 2026 13:10
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from af6d5ad to 623afcc Compare January 23, 2026 18:50
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 623afcc to a514369 Compare February 2, 2026 19:42
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 6f3c010 to 9025326 Compare February 18, 2026 15:56
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 9025326 to 050dcdb Compare February 22, 2026 17:10
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 31db873 to 4ff43e5 Compare March 12, 2026 12:49
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 4ff43e5 to f431633 Compare April 1, 2026 19:06
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f431633 to c250aa2 Compare April 8, 2026 20:04
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 725864e to d07ebf9 Compare April 19, 2026 09:33
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d07ebf9 to 1d65fe4 Compare April 29, 2026 19:05
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1d65fe4 to 0fee166 Compare April 30, 2026 15:50
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 30, 2026 •
edited
Loading

⚠️ 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: package-lock.json
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: ts-log@3.0.2
npm ERR! notsup Not compatible with your version of node/npm: ts-log@3.0.2
npm ERR! notsup Required: {"node":">=20","npm":">=10"}
npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v24.16.0"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-06-02T15_04_18_200Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants