Releases: graphql-hive/router
node-addon 0.0.18 (2026-04-13)
Fixes
Fix planning for conditional inline fragments and field conditions
Fixed a query-planner bug where directive-only inline fragments (using @include/@skip without an explicit type condition) could fail during normalization/planning for deeply nested operations.
This update improves planner handling for conditional selections and adds regression tests to prevent these failures in the future.
hive-router 0.0.47 (2026-04-13)
Fixes
- correct timeout error message (#901)
- Version bump to fix release issues
Fix timeout error message to include the timeout duration instead of the endpoint URL
Previously by mistake, the error message for subgraph request timeouts included the endpoint URL instead of the timeout duration like Request to subgraph timed out after http://ACCOUNT_ENDPOINT:PORT/accounts milliseconds. This change simplifies the error message like Request to subgraph timed out.
Fix planning for conditional inline fragments and field conditions
Fixed a query-planner bug where directive-only inline fragments (using @include/@skip without an explicit type condition) could fail during normalization/planning for deeply nested operations.
This update improves planner handling for conditional selections and adds regression tests to prevent these failures in the future.
Replace GraphiQL with Hive Laboratory
The Laboratory is Hive's powerful GraphQL playground that provides a comprehensive environment for exploring, testing, and experimenting with your GraphQL APIs. Whether you're developing new queries, debugging issues, or sharing operations with your team, the Laboratory offers all the tools you need.
Read more about Hive Laboratory in the introduction blog post or the documentation.
Breaking Changes:
The top-level config option has been renamed.
- graphiql:
+ laboratory:
enabled: trueSo was the environment variable override.
- GRAPHIQL_ENABLED=true
+ LABORATORY_ENABLED=truehive-router-query-planner 2.5.2 (2026-04-13)
Fixes
- planning for conditional inline fragments and field conditions (#894)
- Version bump to fix release issues
Fix planning for conditional inline fragments and field conditions
Fixed a query-planner bug where directive-only inline fragments (using @include/@skip without an explicit type condition) could fail during normalization/planning for deeply nested operations.
This update improves planner handling for conditional selections and adds regression tests to prevent these failures in the future.
hive-router-plan-executor 6.9.3 (2026-04-13)
Fixes
- correct timeout error message (#901)
- Version bump to fix release issues
Fix timeout error message to include the timeout duration instead of the endpoint URL
Previously by mistake, the error message for subgraph request timeouts included the endpoint URL instead of the timeout duration like Request to subgraph timed out after http://ACCOUNT_ENDPOINT:PORT/accounts milliseconds. This change simplifies the error message like Request to subgraph timed out.
Fix planning for conditional inline fragments and field conditions
Fixed a query-planner bug where directive-only inline fragments (using @include/@skip without an explicit type condition) could fail during normalization/planning for deeply nested operations.
This update improves planner handling for conditional selections and adds regression tests to prevent these failures in the future.
hive-router-internal 0.0.16 (2026-04-13)
Fixes
- Version bump to fix release issues
hive-router-config 0.0.28 (2026-04-13)
Fixes
- Version bump to fix release issues
Replace GraphiQL with Hive Laboratory
The Laboratory is Hive's powerful GraphQL playground that provides a comprehensive environment for exploring, testing, and experimenting with your GraphQL APIs. Whether you're developing new queries, debugging issues, or sharing operations with your team, the Laboratory offers all the tools you need.
Read more about Hive Laboratory in the introduction blog post or the documentation.
Breaking Changes:
The top-level config option has been renamed.
- graphiql:
+ laboratory:
enabled: trueSo was the environment variable override.
- GRAPHIQL_ENABLED=true
+ LABORATORY_ENABLED=truehive-router 0.0.46 (2026-04-12)
Fixes
Replace GraphiQL with Hive Laboratory
The Laboratory is Hive's powerful GraphQL playground that provides a comprehensive environment for exploring, testing, and experimenting with your GraphQL APIs. Whether you're developing new queries, debugging issues, or sharing operations with your team, the Laboratory offers all the tools you need.
Read more about Hive Laboratory in the introduction blog post or the documentation.
Breaking Changes:
The top-level config option has been renamed.
- graphiql:
+ laboratory:
enabled: trueSo was the environment variable override.
- GRAPHIQL_ENABLED=true
+ LABORATORY_ENABLED=truehive-router-config 0.0.27 (2026-04-12)
Fixes
Replace GraphiQL with Hive Laboratory
The Laboratory is Hive's powerful GraphQL playground that provides a comprehensive environment for exploring, testing, and experimenting with your GraphQL APIs. Whether you're developing new queries, debugging issues, or sharing operations with your team, the Laboratory offers all the tools you need.
Read more about Hive Laboratory in the introduction blog post or the documentation.
Breaking Changes:
The top-level config option has been renamed.
- graphiql:
+ laboratory:
enabled: trueSo was the environment variable override.
- GRAPHIQL_ENABLED=true
+ LABORATORY_ENABLED=truenode-addon 0.0.17 (2026-04-01)
Fixes
- This patch includes the fixes in the query planner including the fixes for mismatch handling so conflicting fields are tracked by response key (alias-aware), and internal alias rewrites restore the original client-facing key (alias-or-name) instead of always the schema field name.
hive-router 0.0.45 (2026-03-31)
Fixes
- preserve client aliases in mismatch output rewrites (#870)
Preserve client aliases in mismatch rewrites
Fixed query planner mismatch handling so conflicting fields are tracked by response key (alias-aware), and internal alias rewrites restore the original client-facing key (alias-or-name) instead of always the schema field name.