-
Notifications
You must be signed in to change notification settings - Fork 122
docs: change detection upgrade product update #7322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
35 changes: 35 additions & 0 deletions
35
...cs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| --- | ||
| title: Enhanced Schema Change Detection with Directive Support and Input Value Tracking | ||
| description: | ||
| A major upgrade to change detection, with more accurate severity levels and directive support. | ||
| date: 2025-11-27 | ||
| authors: [jdolle] | ||
| --- | ||
|
|
||
| Breaking change detection is complicated, but it's an incredibly valuable tool for any API. In our | ||
| latest release, we upgraded this detection to make breaking changes even more accurate and provide a | ||
| more complete set of changes for schema checks. | ||
|
|
||
| These have been highly requested features, but our hope is that this change goes mostly unnoticed | ||
| because that means it's working and that the changes are tracked accurately. | ||
|
|
||
| The technical set of changes are: | ||
|
|
||
| - `FieldDeprecationRemoved` severity is changing from "dangerous" to "non-breaking". This is because | ||
| deprecation does not impact behavior. | ||
| - `InputFieldAdded` is now "non-breaking" IF a default value is set for the input. Previously only | ||
| nullability was taken into account. This is because the default value will be provided | ||
| automatically, so non-nullable inputs still don't need passed by clients. | ||
| - A redundant DeprecationAdded and DeprecationRemoved change was removed. | ||
| - And `DirectiveUsage` changes are being tracked. E.g. `DirectiveUsageEnumRemoved` and | ||
| `DirectiveUsageObjectAdded`. A similar set of usage events were added for arguments as well. | ||
|
|
||
| --- | ||
|
|
||
| This upgrade also lays the foundation for the upcoming feature, schema proposals, which is powered | ||
| by [GraphQL Inspector](https://the-guild.dev/graphql/inspector) for change capture and rebasing | ||
| changes on top of schemas. | ||
|
|
||
| For more insights on the schema proposals work being done, refer to our | ||
| [Schema Proposal Review](https://the-guild.dev/graphql/hive/product-updates/2025-09-03-schema-proposals) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| update. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This phrasing is a bit awkward. A clearer and more grammatically correct explanation would improve readability.