chore: release

[theguild-bot]

🤖 New release

• hive-router-config: 0.0.10 -> 0.0.11 (✓ API compatible changes)
• hive-router-plan-executor: 6.0.0 -> 6.0.1 (✓ API compatible changes)
• hive-router: 0.0.15 -> 0.0.16 (✓ API compatible changes)

Changelog

hive-router-config

0.0.11 - 2025-10-31

Refactoring

• (jwt) improve the implementation of jwt plugin and expose it to expressions (#534)

hive-router-plan-executor

6.0.1 - 2025-10-31

Refactoring

• (jwt) improve the implementation of jwt plugin and expose it to expressions (#534)
• (executor, router) define ClientRequestDetails only once and avoid all clones, improve how coerce_variables is done (#532)

hive-router

0.0.16 - 2025-10-31

Refactoring

• (jwt) improve the implementation of jwt plugin and expose it to expressions (#534)
• (executor, router) define ClientRequestDetails only once and avoid all clones, improve how coerce_variables is done (#532)

---

This PR was generated with release-plz.

[gemini-code-assist]

Summary of Changes

Hello @theguild-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request constitutes a new release across several core hive-router ecosystem packages, bringing a mix of new features, critical bug fixes, and a significant breaking change. The updates aim to enhance the router's capabilities with more flexible configuration and GraphQL federation support, while also improving the robustness of error handling. Developers should note the API breaking change in hive-router-plan-executor when upgrading.

Highlights

• Breaking Change in hive-router-plan-executor: The hive-router-plan-executor package has a breaking API change, moving from version 5.0.0 to 6.0.0. This is due to the removal or renaming of the PlanExecutionError enum, which was previously publicly visible.
• New Features Across Packages: Several packages introduce new features, including support for label overrides using the @override directive and enhanced configuration options. The hive-router-config and hive-router packages now allow configuration overrides via environment variables and the ability to enable/disable GraphiQL through configuration.
• Bug Fix for Federation v1 Introspection: A bug affecting introspection for Federation v1 supergraphs has been fixed in the hive-router-query-planner and hive-router packages, improving compatibility and reliability.
• Improved Error Handling: The hive-router-plan-executor and hive-router packages have undergone refactoring to add more context to PlanExecutionError, which should aid in debugging and error resolution.
• Version Bumps: All affected packages (hive-router, hive-router-config, hive-router-plan-executor, hive-router-query-planner) have received version updates, reflecting the new features, bug fixes, and the breaking change.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR updates the versions of several hive-router components and their dependencies in the Cargo.lock and Cargo.toml files. It also updates the CHANGELOG.md files for each component to reflect the new versions and associated changes. The most significant change is the upgrade of hive-router-plan-executor from version 5.0.0 to 6.0.0, which includes API breaking changes. The review focuses on ensuring adherence to the performance-first style guide, particularly regarding tracing and logging in hot paths.

[github-actions]

✅ k6-benchmark results

     ✓ response code was 200
     ✓ no graphql errors
     ✓ valid response structure

     █ setup

     checks.........................: 100.00% ✓ 215022      ✗ 0    
     data_received..................: 6.3 GB  209 MB/s
     data_sent......................: 84 MB   2.8 MB/s
     http_req_blocked...............: avg=2.74µs   min=701ns   med=1.82µs  max=4.67ms   p(90)=2.62µs  p(95)=3.01µs  
     http_req_connecting............: avg=188ns    min=0s      med=0s      max=985.53µs p(90)=0s      p(95)=0s      
     http_req_duration..............: avg=20.49ms  min=2.33ms  med=19.55ms max=207.56ms p(90)=27.79ms p(95)=30.98ms 
       { expected_response:true }...: avg=20.49ms  min=2.33ms  med=19.55ms max=207.56ms p(90)=27.79ms p(95)=30.98ms 
     http_req_failed................: 0.00%   ✓ 0           ✗ 71694
     http_req_receiving.............: avg=159.41µs min=25.79µs med=40.56µs max=150.34ms p(90)=85.84µs p(95)=370.25µs
     http_req_sending...............: avg=22.47µs  min=5.75µs  med=10.78µs max=22.99ms  p(90)=16.35µs p(95)=28.2µs  
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s      max=0s       p(90)=0s      p(95)=0s      
     http_req_waiting...............: avg=20.31ms  min=2.28ms  med=19.43ms max=58.21ms  p(90)=27.52ms p(95)=30.71ms 
     http_reqs......................: 71694   2384.24991/s
     iteration_duration.............: avg=20.92ms  min=6.44ms  med=19.91ms max=247.28ms p(90)=28.25ms p(95)=31.48ms 
     iterations.....................: 71674   2383.584792/s
     vus............................: 50      min=50        max=50 
     vus_max........................: 50      min=50        max=50 

[github-actions]

🐋 This PR was built and pushed to the following Docker images:

Image Names: ghcr.io/graphql-hive/router

Platforms: linux/amd64,linux/arm64

Image Tags: ghcr.io/graphql-hive/router:pr-530 ghcr.io/graphql-hive/router:sha-3a8d250

Docker metadata

{
"buildx.build.ref": "builder-a6a72fda-cd50-4fac-a8d4-f62e6cf679f7/builder-a6a72fda-cd50-4fac-a8d4-f62e6cf679f70/j5opinxoq7a2dfepq5rebu03i",
"containerimage.descriptor": {
  "mediaType": "application/vnd.oci.image.index.v1+json",
  "digest": "sha256:d9f23837ad2cc42746e3ecacdbf032551261bcb65e975e63ff364c0aa4f29831",
  "size": 1609
},
"containerimage.digest": "sha256:d9f23837ad2cc42746e3ecacdbf032551261bcb65e975e63ff364c0aa4f29831",
"image.name": "ghcr.io/graphql-hive/router:pr-530,ghcr.io/graphql-hive/router:sha-3a8d250"
}