Skip to content

chore: update dependency @graphql-tools/utils to ^10.11.0#11318

Merged
dhmlau merged 1 commit intomasterfrom
renovate/graphql-tools-monorepo
Nov 30, 2025
Merged

chore: update dependency @graphql-tools/utils to ^10.11.0#11318
dhmlau merged 1 commit intomasterfrom
renovate/graphql-tools-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-tools/utils (source) ^10.10.3 -> ^10.11.0 age adoption passing confidence

Release Notes

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)
      }
    }

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 Nov 30, 2025
@renovate renovate bot requested a review from raymondfeng as a code owner November 30, 2025 02:46
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from f4bbca5 to 0f8aa0e Compare November 30, 2025 02:53
@coveralls
Copy link

coveralls commented Nov 30, 2025

Pull Request Test Coverage Report for Build 19806498081

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage decreased (-0.008%) to 54.898%

Files with Coverage Reduction New Missed Lines %
packages/core/src/application.ts 1 70.28%
Totals Coverage Status
Change from base Build 19806480349: -0.008%
Covered Lines: 9572
Relevant Lines: 12457

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from 0f8aa0e to a7fa08c Compare November 30, 2025 03:39
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from a7fa08c to 7fec8c3 Compare November 30, 2025 23:29
@dhmlau dhmlau merged commit c9c2b75 into master Nov 30, 2025
13 checks passed
@dhmlau dhmlau deleted the renovate/graphql-tools-monorepo branch November 30, 2025 23:54
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.

2 participants