Skip to content

Update graphqlcodegenerator monorepo (major)#22

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

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

Conversation

@renovate

@renovate renovate Bot commented Feb 24, 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.6.2 → ^7.0.0 age confidence
@graphql-codegen/typed-document-node (source) ^2.2.8 → ^7.0.0 age confidence
@graphql-codegen/typescript (source) ^2.4.8 → ^6.0.0 age confidence
@graphql-codegen/typescript-operations (source) ^2.3.5 → ^6.0.0 age confidence
@graphql-codegen/typescript-resolvers (source) ^2.6.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

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:

    yarn 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

v3.2.1

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.

@renovate

renovate Bot commented Feb 24, 2023 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠ 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
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: jest@27.5.1
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^29.0.0" from ts-jest@29.1.1
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/ece5d0/3577bd/cache/others/npm/_logs/2023-07-26T09_01_06_265Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/ece5d0/3577bd/cache/others/npm/_logs/2023-07-26T09_01_06_265Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d277185 to d1ead2b Compare May 30, 2023 05:49
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo to v3 (major) chore(deps): update graphqlcodegenerator monorepo (major) May 30, 2023
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d1ead2b to f0a91c3 Compare July 26, 2023 09:01
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f0a91c3 to 2a5c6dd Compare August 11, 2025 03:45
@renovate

renovate Bot commented Aug 11, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ 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 ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: jest@27.5.1
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^29.0.0 || ^30.0.0" from ts-jest@29.4.11
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

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

@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 5059285 to dfddb60 Compare August 22, 2025 04:00
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from a4a0214 to 05abe09 Compare September 2, 2025 11:57
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 05abe09 to 20be54d Compare September 9, 2025 15:50
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 27ef56a to 24a205f Compare October 1, 2025 18:58
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 24a205f to a467575 Compare October 6, 2025 11:54
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a467575 to e13b6eb Compare October 23, 2025 16:13
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from e13b6eb to d1cd65a Compare November 2, 2025 00:07
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 5826bed to 73bf0d0 Compare November 22, 2025 03:42
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 7fa6cad to f7287db Compare December 4, 2025 23:33
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f7287db to 35f3ac8 Compare December 20, 2025 04:10
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 35f3ac8 to bbbfe59 Compare January 1, 2026 01:36
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 2c28d65 to 7f366b9 Compare January 12, 2026 11:13
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 414438a to a5dea02 Compare January 24, 2026 15:55
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from a5dea02 to 2b440fb Compare February 3, 2026 07:39
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from ec1858a to debdbf1 Compare February 18, 2026 23:46
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from debdbf1 to 610e841 Compare February 24, 2026 06:45
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from d206b2e to d29cd91 Compare March 14, 2026 06:30
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d29cd91 to 9aecd02 Compare April 15, 2026 18:38
@renovate renovate Bot changed the title chore(deps): update graphqlcodegenerator monorepo (major) Update graphqlcodegenerator monorepo (major) Apr 15, 2026
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 9aecd02 to 02af487 Compare April 19, 2026 05:05
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 3138fdc to 3e79b88 Compare May 6, 2026 19:57
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 3cad71d to e528c5d Compare May 13, 2026 07:58
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from e528c5d to 1cb1adf Compare May 23, 2026 03:46
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from af799c5 to 11618cf Compare June 3, 2026 03:55
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 11618cf to 54f4935 Compare June 12, 2026 14:42
@socket-security

socket-security Bot commented Jun 12, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updated@​graphql-codegen/​typed-document-node@​2.3.1 ⏵ 7.0.3100 +110067 +198 -1100
Updated@​graphql-codegen/​typescript-resolvers@​2.7.1 ⏵ 6.0.2100 +110070 +199100
Updated@​graphql-codegen/​typescript@​2.7.1 ⏵ 6.0.2100 +110070 +198100
Updated@​graphql-codegen/​typescript-operations@​2.5.1 ⏵ 6.0.310010071 +398 -1100
Updated@​graphql-codegen/​cli@​2.8.0 ⏵ 7.1.296 +110077 +399 +1100

View full report

@socket-security

socket-security Bot commented Jun 12, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @graphql-tools/github-loader is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ? → npm/@graphql-codegen/cli@7.1.2 → npm/@graphql-tools/github-loader@9.1.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@graphql-tools/github-loader@9.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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