deps(deps): bump graphql from 16.14.2 to 17.0.2 - #28
Conversation
Bumps [graphql](https://github.com/graphql/graphql-js) from 16.14.2 to 17.0.2. - [Release notes](https://github.com/graphql/graphql-js/releases) - [Commits](graphql/graphql-js@v16.14.2...v17.0.2) --- updated-dependencies: - dependency-name: graphql dependency-version: 17.0.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
📊 Coverage Report
Threshold: ≥95% ✅ All coverage dimensions meet the threshold. |
🔄 Code Analyzer — Review in ProgressThe automated review is currently running. This comment will be replaced with a full report once the analysis completes. ⏳ Status: Running security, standards, and code-quality checks... Last updated: 2026-08-03T01:18:05.315Z |
|
The review encountered issues:
Please check the workflow logs for details. 🤖 Generated by Code Analyzer |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps graphql from 16.14.2 to 17.0.2.
Release notes
Sourced from graphql's releases.
... (truncated)
Commits
71606d7chore(release): v17.0.2101de34fix: detect default-value changes on input object fields (#4832)82da713fix(mapSchemaConfig): fix context for schema argument mapper (#4829)9617473chore(release): v17.0.1851bd6achore(release): protect latest release channels (#4825)c471d36fix(diagnostics): emit asyncStart after promise settlement to match native `t...3f3895fchore(npm): remove obsolete ESM-only package build (#4823)c7e494achore(release): v17.0.0d977f66docs: post 17.rc-0 update (#4817)39f865fdocs: document@experimental_disableErrorPropagation(#4820)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)