Skip to content

Update graphqlcodegenerator monorepo (major) - #57

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

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

Conversation

@renovate

@renovate renovate Bot commented Mar 18, 2023

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/cli (source) 2.13.67.4.0 age confidence
@graphql-codegen/typescript (source) 2.7.46.1.0 age confidence
@graphql-codegen/typescript-operations (source) 2.5.46.1.6 age confidence

Release Notes

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

v7.4.0

Compare Source

Minor Changes
  • #​10928
    90229a5
    Thanks @​eddeee888! - Add
    contentComparison?: 'cache-first' | 'disk' to control disk-vs-cache write comparison in watch
    mode.

    In watch mode the CLI caches the hash of the content it last wrote per file and compares new
    output against that cached hash to skip redundant writes. This assumes generated output is a pure
    function of the codegen inputs. An output whose content depends on the file's existing content
    (e.g. a preset that reads the file and rewrites part of it) breaks that assumption: if the file is
    changed on disk and codegen regenerates content identical to a previous run, the cached hash still
    matches and the write is skipped, so the on-disk change is never corrected.

    contentComparison: 'disk' opts an output into comparing the generated content against the file
    on disk instead of the in-memory record of what codegen last wrote, so the file is rewritten when
    it was changed externally. It can be set:

    • by a preset, on the GenerateOptions it returns from buildGeneratesSection, or
    • on the output config (generates[output].contentComparison) for any output, including plain
      plugin outputs without a preset.

    When both are present, the preset's value takes precedence. The default, 'cache-first', keeps
    the existing in-memory-cache behaviour for outputs that are a pure function of their inputs.

Patch Changes
  • #​10930
    448431a
    Thanks @​eddeee888! - Fix overwrite being ignored for
    preset-based generates outputs.

    A generates entry that used a preset and set overwrite (e.g.
    overwrite: { removeStaleFiles: false }) had that setting silently ignored, so in watch mode its
    generated files could still be deleted as stale.

    The CLI resolved overwrite per generated file by looking the file's path up in
    config.generates. That fails for a preset: its generates entry is keyed by the preset's
    baseOutputDir, not by any generated file's path (and a preset can emit files outside that
    directory), and the lookup additionally required a plugins key that preset entries don't have.
    Both cases fell through to the global config.overwrite (default true).

  • Updated dependencies
    [90229a5,
    448431a]:

v7.3.1

Compare Source

Patch Changes
  • #​10924
    0c8f5ba
    Thanks @​eddeee888! - Fix profiler output not being written to the
    filesystem in watch mode (--profile --watch)

    The profiler trace was only written on the non-watch code path, after the watch-mode early return,
    so a profiled watch session never produced a codegen-*.json file.

    The profiler now writes a fresh trace file after the initial run and after every rebuild, with
    each file containing only that run's events. A failed rebuild does not produce a trace and its
    events are discarded so they don't leak into the next successful run.

    The Profiler now owns its own trace lifecycle:

    • a new clear() method starts a new trace
    • a new outputName property provides the filename for the current trace (null for the noop
      profiler)
    • filename generation was removed from CodegenContext
  • Updated dependencies
    [0c8f5ba]:

v7.3.0

Compare Source

Minor Changes
  • #​10921
    58cdb31
    Thanks @​eddeee888! - Extend overwrite with
    overwrite.removeStaleFiles and overwrite.updateExistingFiles

    overwrite was being used to both remove stale files in watch mode and update existing files.
    Some plugins such as Server Preset may dynamically return files to write between watch runs (for
    performance purposes).

    The overwrite can now take an object with overwrite.removeStaleFiles and
    overwrite.updateExistingFiles fields to allow granular control over actions.

    This is not a breaking change because overwrite=true|false still works.

Patch Changes

v7.2.0

Compare Source

Minor Changes
Patch Changes

v7.1.3

Compare Source

Patch Changes
  • #​10335
    3280ace
    Thanks @​Diluka! - Fix graphql-config loading order to correctly
    detect codegen projects

    Previously, a graphql-config file like this failed:

    projects:
      default:
        schema: 'default/schema.graphql'
      project1:
        schema: 'project1/schema.graphql'
        extensions:
          codegen:
            generates:
              'project1/__generated__/types.ts':
                plugins: ['typescript']

    This is because the default project doesn't have a codegen extension, which caused previous
    logic to short circuit before reading project1's config.

    The fix reads every named project first, before reading the default project to exhaustively go
    through every single project.

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

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes
Patch Changes

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 093b3fb to 1ebbaec Compare April 17, 2023 12:34
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1ebbaec to 1172517 Compare May 28, 2023 11:22
@renovate renovate Bot changed the title Update graphqlcodegenerator monorepo to v3 (major) Update graphqlcodegenerator monorepo to v4 (major) May 28, 2023
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1172517 to 2bb652f Compare June 1, 2023 20:02
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 2bb652f to bade1ea Compare June 19, 2023 10:37
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from bade1ea to 41aa53f Compare July 25, 2023 10:17
@renovate renovate Bot changed the title Update graphqlcodegenerator monorepo to v4 (major) Update graphqlcodegenerator monorepo (major) Jul 25, 2023
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 41aa53f to 247f04f Compare February 6, 2024 15:17
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 3d434c7 to f29b7e1 Compare February 22, 2024 21:43
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f29b7e1 to 8d76439 Compare May 17, 2024 17:05
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 987d941 to f1a5d4d Compare July 2, 2024 10:58
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f1a5d4d to 2b5d04f Compare October 7, 2024 16:01
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 2b5d04f to a5efa1c Compare October 28, 2024 13:40
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a5efa1c to 7fa9341 Compare November 22, 2024 21:43
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 7fa9341 to b4f2a37 Compare January 28, 2025 12:35
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from c5c7312 to 3fef56d Compare February 19, 2025 17:07
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 3fef56d to e7f036b Compare February 23, 2025 21:39
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from e7f036b to f34881e Compare March 27, 2025 12:38
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f34881e to d2381ef Compare May 6, 2025 17:03
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d2381ef to be2c018 Compare June 6, 2025 19:13
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0bfde76 to c86f0a5 Compare August 13, 2025 11:48
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from c86f0a5 to 63123b0 Compare August 19, 2025 17:38
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 63123b0 to aff8f22 Compare August 31, 2025 14:17
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from aff8f22 to 0b56b3c Compare September 7, 2025 21:58
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 93bcd43 to 9d21e67 Compare September 29, 2025 16:53
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from dd40ed0 to 5efa217 Compare January 11, 2026 13:57
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from f514e5d to 03af106 Compare January 23, 2026 18:30
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 03af106 to 0c537df Compare February 2, 2026 14:58
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 696e3f7 to ef77737 Compare February 18, 2026 15:05
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from ef77737 to d00810a Compare February 22, 2026 17:39
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from b0b6a72 to d9e5336 Compare March 12, 2026 13:00
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d9e5336 to 3e21693 Compare March 13, 2026 15:21
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from bba80b1 to 981c11a Compare April 8, 2026 14:55
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from dc4a7aa to 9d8996a Compare April 18, 2026 18:42
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 713aebc to 26d7dbe Compare April 30, 2026 16:51
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 1ba9faf to 1f71d22 Compare May 12, 2026 17:52
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 1f71d22 to e8ec14f Compare May 18, 2026 10:03
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from 50432ed to bb72474 Compare June 1, 2026 18:42
@renovate
renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from bb72474 to 2d2efb4 Compare June 11, 2026 12:15
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