Skip to content

Update graphql-codegen (major)#60

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphql-codegen
Open

Update graphql-codegen (major)#60
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-graphql-codegen

Conversation

@renovate

@renovate renovate Bot commented Jun 2, 2023 •
edited
Loading

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.1 → 7.2.0 age confidence
@graphql-codegen/gql-tag-operations-preset (source) 1.6.0 → 2.1.0 age confidence

Release Notes

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

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

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes

  • #​9151
    b7dacb21f
    Thanks
    @​'./user/schema.mappers#UserMapper',! -
    Add watchPattern config option for generates 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 a watchPattern 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.

    // codegen.ts
const config: CodegenConfig = {
  schema: 'src/schema/**/*.graphql',
  generates: {
    'src/schema/types.ts': {
      plugins: ['typescript', 'typescript-resolvers'],
      config: {
        mappers: {

          Book: './book/schema.mappers#BookMapper',
        },
      }
      watchPattern: 'src/schema/**/*.mappers.ts', // Watches mapper files in `watch` mode. Use an array for multiple patterns e.g. `['src/*.pattern1.ts','src/*.pattern2.ts']`
    },
  },
};

    Then, run Codegen CLI in watch mode:

    pnpm graphql-codegen --watch

    Now, updating *.mappers.ts files re-runs Codegen! 🎉

    Note: watchPattern is only used in watch mode i.e. running CLI with --watch flag.

Patch Changes

v3.2.2

Compare Source

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.

@vercel

vercel Bot commented Jun 2, 2023 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
supabase-graphql-example Ready Ready Preview, Comment Jun 16, 2026 4:06pm

Request Review

@renovate renovate Bot added the dependencies label Jun 2, 2023
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from d974acf to c89adeb Compare July 25, 2023 09:34
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from c89adeb to e851850 Compare February 6, 2024 15:16
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from e851850 to 0f0e05a Compare August 7, 2024 22:43
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 0f0e05a to 189ca51 Compare October 7, 2024 15:21
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 189ca51 to 9db887c Compare January 28, 2025 13:41
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 9db887c to 4b69e2e Compare February 13, 2025 16:04
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 4b69e2e to 6f1f587 Compare May 6, 2025 20:25
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 6f1f587 to fbb776a Compare June 5, 2025 13:52
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from fbb776a to e785e7b Compare August 4, 2025 22:27
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from e785e7b to e87c085 Compare August 10, 2025 14:02
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from e87c085 to 0700169 Compare August 13, 2025 14:05
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 0700169 to 132a63f Compare August 19, 2025 18:32
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 132a63f to 2eaf930 Compare August 31, 2025 09:42
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 2eaf930 to 230b25c Compare September 7, 2025 20:05
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 4012de6 to 437a62b Compare January 2, 2026 03:51
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 437a62b to 8c3734f Compare January 8, 2026 19:16
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 8c3734f to 148ea05 Compare January 11, 2026 13:11
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 148ea05 to 7fae93b Compare January 22, 2026 11:34
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 7fae93b to 02a3665 Compare January 23, 2026 20:40
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 02a3665 to ffec4d6 Compare February 4, 2026 08:13
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from ffec4d6 to 2c7bdef Compare February 12, 2026 10:41
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 2c7bdef to a70e9de Compare February 17, 2026 20:58
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from a70e9de to 11f82c5 Compare February 22, 2026 17:49
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 11f82c5 to dff861f Compare March 5, 2026 16:08
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from dff861f to 0c8d1c5 Compare March 6, 2026 18:45
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 0c8d1c5 to 37f170c Compare March 14, 2026 12:11
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 37f170c to 35c6c31 Compare May 2, 2026 16:05
@renovate renovate Bot changed the title chore(deps): update graphql-codegen (major) Update graphql-codegen (major) May 2, 2026
@renovate renovate Bot force-pushed the renovate/major-graphql-codegen branch from 35c6c31 to 2d364de Compare May 12, 2026 10:53
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

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants