chore: release

[theguild-bot]

🤖 New release

• hive-router-query-planner: 2.0.1 -> 2.0.2 (✓ API compatible changes)
• hive-router-config: 0.0.9 -> 0.0.10 (✓ API compatible changes)
• hive-router-plan-executor: 5.0.0 -> 6.0.0 (⚠ API breaking changes)
• hive-router: 0.0.14 -> 0.0.15 (✓ API compatible changes)

⚠ hive-router-plan-executor breaking changes

--- failure enum_missing: pub enum removed or renamed ---

Description:
A publicly-visible enum cannot be imported by its prior path. A `pub use` may have been removed, or the enum itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.43.0/src/lints/enum_missing.ron

Failed in:
  enum hive_router_plan_executor::execution::error::PlanExecutionError, previously in file /tmp/.tmph7uk5R/hive-router-plan-executor/src/execution/error.rs:4

Changelog

hive-router-query-planner

2.0.2 - 2025-10-27

Bug Fixes

• (query-planner, router) fix introspection for federation v1 supergraph (#526)

hive-router-config

0.0.10 - 2025-10-27

New Features

• (router) added support for label overrides with @override (#518)
• (config) configuration override using env vars, enable/disable graphiql via config (#519)

hive-router-plan-executor

6.0.0 - 2025-10-27

New Features

• (router) added support for label overrides with @override (#518)

Refactoring

• (error-handling) add context to PlanExecutionError (#513)

hive-router

0.0.15 - 2025-10-27

New Features

• (router) added support for label overrides with @override (#518)
• (config) configuration override using env vars, enable/disable graphiql via config (#519)

Bug Fixes

• (query-planner, router) fix introspection for federation v1 supergraph (#526)

Refactoring

• (error-handling) add context to PlanExecutionError (#513)

---

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 is an automated release that updates the versions of the hive-router-plan-executor and hive-router packages. The hive-router-plan-executor receives a major version bump due to a breaking change related to its PlanExecutionError enum, while hive-router gets a minor version update. Both packages incorporate a refactoring change to enhance error handling by adding context to PlanExecutionError.

Highlights

• Package Version Updates: The hive-router-plan-executor package has been updated from version "5.0.0" to "6.0.0", and the hive-router package has been updated from version "0.0.14" to "0.0.15".
• Breaking Change in hive-router-plan-executor: The hive-router-plan-executor package introduces a breaking change where the PlanExecutionError enum has been removed or renamed, affecting its public API.
• Error Handling Refactoring: Both hive-router-plan-executor and hive-router include a refactoring change to add context to PlanExecutionError.
• Dependency Update: The syn dependency in Cargo.lock has been updated from version "2.0.106" to "2.0.108".

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 pull request handles the automated release of hive-router-plan-executor (v6.0.0) and hive-router (v0.0.15). The changes consist of version bumps in Cargo.toml and Cargo.lock, along with corresponding updates to the changelogs. The changes are consistent across the files and accurately reflect the new versions. I've reviewed the modifications and found no issues. The pull request is good to merge.

[github-actions]

✅ k6-benchmark results

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

     █ setup

     checks.........................: 100.00% ✓ 204321      ✗ 0    
     data_received..................: 6.0 GB  199 MB/s
     data_sent......................: 80 MB   2.7 MB/s
     http_req_blocked...............: avg=3.05µs   min=731ns   med=1.8µs   max=3.8ms    p(90)=2.58µs  p(95)=2.97µs  
     http_req_connecting............: avg=569ns    min=0s      med=0s      max=1.8ms    p(90)=0s      p(95)=0s      
     http_req_duration..............: avg=21.57ms  min=2.2ms   med=20.57ms max=202.56ms p(90)=29.31ms p(95)=32.61ms 
       { expected_response:true }...: avg=21.57ms  min=2.2ms   med=20.57ms max=202.56ms p(90)=29.31ms p(95)=32.61ms 
     http_req_failed................: 0.00%   ✓ 0           ✗ 68127
     http_req_receiving.............: avg=190.53µs min=25.04µs med=40.89µs max=167.73ms p(90)=92.15µs p(95)=414.53µs
     http_req_sending...............: avg=26.88µs  min=5.37µs  med=10.77µs max=27.63ms  p(90)=16.29µs p(95)=27.81µs 
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s      max=0s       p(90)=0s      p(95)=0s      
     http_req_waiting...............: avg=21.35ms  min=2.15ms  med=20.43ms max=64.9ms   p(90)=29.07ms p(95)=32.28ms 
     http_reqs......................: 68127   2266.040764/s
     iteration_duration.............: avg=22.01ms  min=6.95ms  med=20.93ms max=267.75ms p(90)=29.77ms p(95)=33.09ms 
     iterations.....................: 68107   2265.375524/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-529 ghcr.io/graphql-hive/router:sha-9b50210

Docker metadata

{
"buildx.build.ref": "builder-1326ea39-7111-49a0-92c8-b7d7a4e969bd/builder-1326ea39-7111-49a0-92c8-b7d7a4e969bd0/ues42avoynyotgvsmhxaappzj",
"containerimage.descriptor": {
  "mediaType": "application/vnd.oci.image.index.v1+json",
  "digest": "sha256:0b6074ef0ecd75b4ff6654a1a396babbc3a8c27d383df31c6d693838f9dba31b",
  "size": 1609
},
"containerimage.digest": "sha256:0b6074ef0ecd75b4ff6654a1a396babbc3a8c27d383df31c6d693838f9dba31b",
"image.name": "ghcr.io/graphql-hive/router:pr-529,ghcr.io/graphql-hive/router:sha-9b50210"
}