Skip to content

Update graphqlcodegenerator monorepo (major)#11460

Merged
nbudin merged 10 commits into
mainfrom
renovate/major-graphqlcodegenerator-monorepo
May 11, 2026
Merged

Update graphqlcodegenerator monorepo (major)#11460
nbudin merged 10 commits into
mainfrom
renovate/major-graphqlcodegenerator-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 9, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/add (source) 6.0.1 → 7.0.0 age confidence
@graphql-codegen/cli (source) 6.3.1 → 7.0.0 age confidence
@graphql-codegen/fragment-matcher (source) 6.0.1 → 7.0.0 age confidence
@graphql-codegen/introspection (source) 5.0.2 → 6.0.0 age confidence
@graphql-codegen/typed-document-node (source) ^6.0.0 → ^7.0.0 age confidence
@graphql-codegen/typescript (source) 5.0.10 → 6.0.1 age confidence
@graphql-codegen/typescript-operations (source) 5.1.0 → 6.0.2 age confidence

Release Notes

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

v7.0.0

Compare Source

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

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
dotansimha/graphql-code-generator (@​graphql-codegen/fragment-matcher)

v7.0.0

Compare Source

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

v6.0.0

Compare Source

Major Changes
Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typed-document-node)

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

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

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
dotansimha/graphql-code-generator (@​graphql-codegen/typescript-operations)

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! - Fix nullable field optionality in operations

    Previously, a nullable Result field is generated as optional (marked by ? TypeScript modifier)
    by default. This is not correct, because generally at runtime such field can only be null, and
    not undefined (both missing from the object OR undefined). The only exceptions are when fields
    are deferred (using @defer directive) or marked as conditional (using @skip or @include).

    Now, a nullable Result field cannot be optional unless the exceptions are met. This also limits
    avoidOptionals to only target Variables input, since some users may want to force explicit
    null when providing operation variables.

  • #​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: typescript-operations plugin
    now generates enum if it is used in operation.

  • #​10496
    afaace6
    Thanks @​eddeee888! - Conditionally generate input types and output
    enums into target file

  • #​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: Decouple
    typescript-operations plugin from typescript plugin

    Previously, TypeScriptOperationVariablesToObject from typescript-operations was extending from
    typescript plugin. This made it (1) very hard to read, as we need to jump from base class <->
    typescript class <-> typescript-operations class to understand the flow and (2) very hard to
    evolve the two independently (which is the point of this work).

    Since there's not much shared logic anyways, it's simpler to extend the typescript-operations
    class from the base class directly.

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

  • #​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: Operation plugin and Client
    Preset no longer generates optional __typename for result type

    __typenam should not be in the request unless:

    • explicitly requested by the user
    • automatically injected into the request by clients, such as Apollo Clients.

    Note: Apollo Client users can still use nonOptionalTypename: true and
    skipTypeNameForRoot: true to ensure generated types match the runtime behaviour.

  • #​10496
    afaace6
    Thanks @​eddeee888! - Integrate new typescript-operations into
    client-preset

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: config.avoidOptionals now
    only supports object, inputValue, defaultValue

  • #​10496
    afaace6
    Thanks @​eddeee888! - BREAKING CHANGE: rename avoidOptionals.object
    to avoidOptionals.variableValue

Minor Changes

  • #​10496
    afaace6
    Thanks @​eddeee888! - Add support for declarationKind for
    typescript-operations

    • Input: can only be type or interface
    • Variables: no support. It must always be type because it's an alias e.g.
      Variables = Exact<{ something: type }>
    • Result: can only be type or interface
      • Note: when extractAllFieldsToTypes:true or extractAllFieldsToTypesCompact:true, Results
        are used as type alias, so they are forced to be type. There is a console warning for users.

  • #​10496
    afaace6
    Thanks @​eddeee888! - Add importSchemaTypesFrom support

  • #​10496
    afaace6
    Thanks @​eddeee888! - Add generateOperationTypes to
    typescript-operations to allow omitting operation types such as Variables,
    Query/Mutation/Subscription selection set, and Fragment types

  • #​10496
    afaace6
    Thanks @​eddeee888! - Fixing 2 bugs: 1) including enums from
    external fragments; 2) extractAllFieldsToTypesCompact does not create duplicates

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: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 added the dependencies label May 9, 2026
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 11 times, most recently from 920873b to f4403f4 Compare May 11, 2026 15:55
@renovate renovate Bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from f4403f4 to 5e8fad7 Compare May 11, 2026 15:58
nbudin and others added 4 commits May 11, 2026 09:04
@nbudin
Regenerate all code
c27ff84
@nbudin
Fix some nullability issues manually
28a37cb
@nbudin
Harmonize CurrencySelect with its caller
388317e
@nbudin @claude
Refactor ScheduleGrid to use minimum input types
45ff804 
Introduces ScheduleGridTypes.ts with ScheduleGridEventCategory and
ScheduleGridConventionInput — minimum structural types that both the
ScheduleGrid query and the EventAdmin query satisfy — so
useScheduleGridProvider and useMergeCategoriesIntoEvents no longer
depend on the fully-generated convention/event types.

ScheduleEvent is now expressed as an Omit/intersection over
ScheduleGridEventFragment rather than longhand, making it stay in sync
with schema changes automatically. Fields only present in the ScheduleGrid
query (my_rating, short_blurb_html, form_response_attrs_json_with_rendered_markdown,
and the extended registration_policy capacity fields) are made optional.

This removes the as-unknown-as casts from ProspectiveRunSchedule and fixes
a MoneyInput currency_code undefined/null mismatch unmasked by the cleanup.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 11, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

nbudin and others added 5 commits May 11, 2026 11:15
@nbudin @claude
Fix remaining nullability TypeScript errors
12cb9db 
- TimezoneSelect: narrow onChange prop to (value: string | null) => void
- NewRun: initialize title_suffix and schedule_note as null instead of undefined
- NewEvent: use ScheduleEventInput for the prospective run event object, removing excess fields and adding registration_policy: null
- RunFormFields/ProspectiveRunSchedule: narrow event prop type from full EventFieldsFragment to ScheduleEventInput since only id, length_seconds, runs, and schedule-compatible fields are used

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nbudin @claude
Fix TypeScript errors: GraphQL fragment field mismatches
6eebbca 
Narrow component prop types to only require fields they actually use,
resolving mismatches when different queries fetch different subsets.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nbudin @claude
Fix TypeScript errors in LiquidDocs, SignupRoundCard, and NewStaffPos…
d252bbd 
…ition

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nbudin @claude
Fix remaining TypeScript errors from graphql-codegen upgrade
aaebc28 
Adds missing fields (email, expose_in, description) to GraphQL fragments
and generated types, fixes type mismatches caused by the new codegen
emitting `Maybe<T> | undefined` for optional schema fields, and updates
concrete type definitions for AdminOrderType, EditingStaffPosition, etc.
to avoid `Pick` from schema types where optional fields become required
properties with undefined in their union type.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nbudin @claude
Run graphql:codegen to properly regenerate files after graphql changes
67dde5b 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 11, 2026

Code Coverage Report: Only Changed Files listed

Package Base Coverage New Coverage Difference
Overall Coverage 🟢 53.1% 🟢 53.1% ⚪ 0%

Minimum allowed coverage is 0%, this run produced 53.1%

@nbudin nbudin merged commit a2fe6bc into main May 11, 2026
17 checks passed
@nbudin nbudin deleted the renovate/major-graphqlcodegenerator-monorepo branch May 11, 2026 20:15
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.

1 participant

@nbudin