Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 4, 2025

This PR contains the following updates:

Package Change Age Confidence
@graphql-tools/graphql-file-loader (source) 8.0.22 -> 8.1.8 age confidence
@graphql-tools/json-file-loader (source) 8.0.20 -> 8.0.25 age confidence
@graphql-tools/load (source) 8.1.2 -> 8.1.7 age confidence
@graphql-tools/merge (source) 9.1.1 -> 9.1.6 age confidence
@graphql-tools/utils (source) 10.9.1 -> 10.11.0 age confidence

Release Notes

ardatan/graphql-tools (@​graphql-tools/graphql-file-loader)

v8.1.8

Compare Source

Patch Changes

v8.1.7

Compare Source

Patch Changes

v8.1.6

Compare Source

Patch Changes

v8.1.5

Compare Source

Patch Changes

v8.1.4

Compare Source

Patch Changes

v8.1.3

Compare Source

Patch Changes

v8.1.2

Compare Source

Patch Changes

v8.1.1

Compare Source

Patch Changes

v8.1.0

Compare Source

Minor Changes
  • #​7310
    692cfeb
    Thanks @​HunterLarco! - GraphQL schemas in large projects,
    especially monorepos, suffer from fragile and verbose relative import paths that become difficult
    to maintain as projects grow. This change brings TypeScript's popular
    tsconfig.json#paths aliasing syntax to GraphQL
    imports, enabling clean, maintainable import statements across your GraphQL schema files.

    Before - Brittle relative imports:

    #import "../../../shared/models/User.graphql"
    #import "../../../../common/types/Product.graphql"

    After - Clean, semantic aliases:

    #import "@​models/User.graphql"
    #import "@​types/Product.graphql"

    Configuration Example

    {
      mappings: {
        '@​models/*': path.join(__dirname, './models/*'),
        '@​types/*': path.join(__dirname, './shared/types/*'),
      }
    }

    This change is introduced in a backwards compatible way to ensure no existing use cases are broken
    while using familiar patterns to typescript developers for structuring import aliases.

Patch Changes
ardatan/graphql-tools (@​graphql-tools/json-file-loader)

v8.0.25

Compare Source

Patch Changes

v8.0.24

Compare Source

Patch Changes

v8.0.23

Compare Source

Patch Changes

v8.0.22

Compare Source

Patch Changes

v8.0.21

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/load)

v8.1.7

Compare Source

Patch Changes

v8.1.6

Compare Source

Patch Changes

v8.1.5

Compare Source

Patch Changes

v8.1.4

Compare Source

Patch Changes

v8.1.3

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/merge)

v9.1.6

Compare Source

Patch Changes

v9.1.5

Compare Source

Patch Changes

v9.1.4

Compare Source

Patch Changes

v9.1.3

Compare Source

Patch Changes

v9.1.2

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/utils)

v10.11.0

Compare Source

Minor Changes
  • #​7588
    2118a80
    Thanks @​EmrysMyrddin! - Add optional schema coordinate in error
    extensions. This extension allows to precisely identify the source of the error by automated tools
    like tracing or monitoring.

    This new feature is opt-in, you have to enable it using schemaCoordinateInErrors executor
    option.

    Caution: This feature, when enabled, will expose information about your schema. If you need to
    keep your schema private and secret, you should strip this attribute at serialization time before
    sending errors to the client.

    import { parse } from 'graphql'
    import { normalizedExecutor } from '@​graphql-tools/executor'
    import { getSchemaCoordinate } from '@​graphql-tools/utils'
    import schema from './schema'
    
    const result = await normalizedExecutor({
      schema,
      document: parse(`...`),
      schemaCoordinateInErrors: true // enable adding schema coordinate to graphql errors
    })
    
    if (result.errors) {
      for (const error of result.errors) {
        console.log('Error in resolver ', error.coordinate, ':', error.message)
        // or with `getSchemaCoordinate` util, to workaround types if needed
        console.log('Error in resolver', getSchemaCoordinate(error), ':', error.message)
      }
    }

v10.10.3

Compare Source

Patch Changes
  • #​7683
    2fe123a
    Thanks @​ardatan! - Revert
    #​7683 which can cause unexpected breaking changes so
    as before the schema extension node will always be converted to a schema definition node

v10.10.2

Compare Source

Patch Changes
  • #​7679
    dddc5f6
    Thanks @​ardatan! - Support "federation/subgraph style" schemas in
    astFromSchema and printSchemaWithDirectives

    If a GraphQLSchema doesn't have any defined operation types, we should print the schema
    definition as an extension rather than omitting it entirely. They are not a valid schema on their
    own, but they are valid subgraph schemas in a federation setup, and it is possible to build such
    schemas with assumeValid options.

    // A schema without defined root types
    buildSchema(
      /* GraphQL */ `
        extend schema @​link(url: "https://specs.apollo.dev/federation/v2.0", import: ["@​key"])
    
        type User @​key(fields: "id") {
          id: ID!
          username: String
        }
      `,
      { assumeValid: true, assumeValidSDL: true }
    )

v10.10.1

Compare Source

Patch Changes

v10.10.0

Compare Source

Minor Changes
  • #​5269
    fded91e
    Thanks @​uroslates! - Add default values to the arguments

    When the schema is like following;

    type Query {
        getAllPages(currentPage: Int = 0, pageSize: Int = 10, pageType: getAllPages_pageType = ContentPage, sort: String = "asc"): PagesList
    }
    
    enum getAllPages_pageType {
        ContentPage
        CategoryPage
        CatalogPage
    }
    
    type PagesList {
        ...
    }

    The generated operation will be like following;

    query getAllPages_query($currentPage: Int = 0, $pageSize: Int = 10, $pageType: getAllPages_pageType = ContentPage, $sort: String = "asc") {
        getAllPages(currentPage: $currentPage, pageSize: $pageSize, pageType: $pageType, sort: $sort) {
            ...
        }
    }
Patch Changes
  • #​7012
    fd105f4
    Thanks @​ardatan! - Fix the bug in mergeDeep;

    The following inputs and outputs are corrected;

    • mergeDeep([{a:2}, undefined]) - Any nullish values should be ignored so it should return
      {a:2}
    • mergeDeep([]) - no sources should return undefined
    • mergeDeep([undefined]) - no sources should return undefined
  • #​5294
    3b99a9b
    Thanks @​n1ru4l! - Do not map builtin scalars


Configuration

📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Warsaw, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 added the dependencies Pull requests that update a dependency file label Dec 4, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

💻 Website Preview

The latest changes are available as preview in: https://pr-1750.graphql-config.pages.dev

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants