From 2547e5f056f3586a7738d0b8e3186bc179c36632 Mon Sep 17 00:00:00 2001 From: jdolle <1841898+jdolle@users.noreply.github.com> Date: Tue, 25 Nov 2025 16:57:28 -0800 Subject: [PATCH 1/2] docs: change detection upgrade product update --- .../page.mdx | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx diff --git a/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx b/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx new file mode 100644 index 0000000000..1f22e20da8 --- /dev/null +++ b/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx @@ -0,0 +1,38 @@ +--- +title: Change Detection Upgrade +description: + GraphQL Inspector version 7.x is a major upgrade to "diff" 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. In our latest +release, we upgraded our version of [GraphQL Inspector](https://the-guild.dev/graphql/inspector), +which is used by Hive for change detection. + +What this means for you is a more complete set of changes get displayed for checks and schema change +history, and breaking changes are even more accurate. + +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 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) +update. From b1b6fe6c6cb00f50a383ce878f145ccd28aa69e3 Mon Sep 17 00:00:00 2001 From: jdolle <1841898+jdolle@users.noreply.github.com> Date: Wed, 26 Nov 2025 13:56:51 -0800 Subject: [PATCH 2/2] Address comments --- .../page.mdx | 21 ++++++++----------- 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx b/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx index 1f22e20da8..8d469be5dd 100644 --- a/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx +++ b/packages/web/docs/src/app/product-updates/(posts)/2025-11-27-change-detection-upgrade/page.mdx @@ -1,21 +1,17 @@ --- -title: Change Detection Upgrade +title: Enhanced Schema Change Detection with Directive Support and Input Value Tracking description: - GraphQL Inspector version 7.x is a major upgrade to "diff" detection, with more accurate severity - levels and directive support. + 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. In our latest -release, we upgraded our version of [GraphQL Inspector](https://the-guild.dev/graphql/inspector), -which is used by Hive for change detection. +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. -What this means for you is a more complete set of changes get displayed for checks and schema change -history, and breaking changes are even more accurate. - -Our hope is that this change goes mostly unnoticed because that means it's working and that the -changes are tracked accurately. +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: @@ -31,7 +27,8 @@ The technical set of changes are: --- This upgrade also lays the foundation for the upcoming feature, schema proposals, which is powered -by GraphQL Inspector for change capture and rebasing changes on top of schemas. +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)