chore: release

[theguild-bot]

🤖 New release

• hive-router-config: 0.0.6 -> 0.0.7 (✓ API compatible changes)
• hive-router-plan-executor: 3.0.0 -> 4.0.0 (⚠ API breaking changes)
• hive-router: 0.0.11 -> 0.0.12 (✓ API compatible changes)

⚠ hive-router-plan-executor breaking changes

--- failure constructible_struct_adds_field: externally-constructible struct adds field ---

Description:
A pub struct constructible with a struct literal has a new pub field. Existing struct literals must be updated to include the new field.
        ref: https://doc.rust-lang.org/reference/expressions/struct-expr.html
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.43.0/src/lints/constructible_struct_adds_field.ron

Failed in:
  field QueryPlanExecutionContext.jwt_auth_forwarding in /tmp/.tmpkLRAw8/router/lib/executor/src/execution/plan.rs:75
  field HttpExecutionRequest.extensions in /tmp/.tmpkLRAw8/router/lib/executor/src/executors/common.rs:36

--- failure function_parameter_count_changed: pub fn parameter count changed ---

Description:
A publicly-visible function now takes a different number of parameters.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#fn-change-arity
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.43.0/src/lints/function_parameter_count_changed.ron

Failed in:
  hive_router_plan_executor::utils::traverse::traverse_and_callback_mut now takes 5 parameters instead of 4, in /tmp/.tmpkLRAw8/router/lib/executor/src/utils/traverse.rs:9

--- failure method_parameter_count_changed: pub method parameter count changed ---

Description:
A publicly-visible method now takes a different number of parameters.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#fn-change-arity
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.43.0/src/lints/method_parameter_count_changed.ron

Failed in:
  hive_router_plan_executor::execution::plan::Executor::new now takes 7 parameters instead of 6, in /tmp/.tmpkLRAw8/router/lib/executor/src/execution/plan.rs:225
  hive_router_plan_executor::context::ExecutionContext::handle_errors now takes 4 parameters instead of 2, in /tmp/.tmpkLRAw8/router/lib/executor/src/context.rs:45

Changelog

hive-router-config

0.0.7 - 2025-10-15

Added

• (router) jwt auth (#455)
• (router) CORS support (#473)
• (router) CSRF prevention for browser requests (#472)

hive-router-plan-executor

4.0.0 - 2025-10-15

Added

• (router) jwt auth (#455)
• (executor) include subgraph name and code to the errors (#477)
• (executor) normalize flatten errors for the final response (#454)

hive-router

0.0.12 - 2025-10-15

Added

• (router) jwt auth (#455)
• (router) CORS support (#473)
• (router) CSRF prevention for browser requests (#472)
• (executor) include subgraph name and code to the errors (#477)
• (executor) normalize flatten errors for the final response (#454)

---

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 performs a routine release for two key components: hive-router-plan-executor and hive-router. The hive-router-plan-executor module receives a major version bump due to necessary API breaking changes, primarily concerning function and method parameter counts. Concurrently, hive-router undergoes a minor version update. Both releases integrate an enhancement focused on standardizing the format of flattened errors in responses, aiming for more consistent error handling.

Highlights

• Major Version Update for hive-router-plan-executor: The hive-router-plan-executor package has been updated from version 3.0.0 to 4.0.0, indicating significant API breaking changes.
• Minor Version Update for hive-router: The hive-router package has been updated from version 0.0.11 to 0.0.12, which includes API compatible changes.
• Breaking Changes Detailed: The breaking changes in hive-router-plan-executor specifically involve changes in parameter counts for the traverse_and_callback_mut function (from 4 to 5 parameters) and the ExecutionContext::handle_errors method (from 2 to 3 parameters).
• Error Normalization Feature: Both updated packages now include functionality to 'normalize flatten errors for the final response', as referenced in PR feat(executor): normalize flatten errors for the final response #454.

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, generated by release-plz, correctly bumps the versions of hive-router-plan-executor to 4.0.0 and hive-router to 0.0.12. The changes in Cargo.toml, Cargo.lock, and the changelogs are consistent with the release. I've added one suggestion to improve the changelog for hive-router-plan-executor to make the breaking changes more explicit for consumers of the library.

[gemini-code-assist]

Since version 4.0.0 is a major release with breaking API changes, it's helpful to explicitly list them in the changelog. This provides better visibility for developers and helps prevent issues during upgrades. I'd suggest adding a Changed section to highlight these breaking changes.

Suggested change

	### Added
	- *(executor)* normalize flatten errors for the final response ([#454](https://github.com/graphql-hive/router/pull/454))
	### Changed
	- **BREAKING**: The function signatures for traverse_and_callback_mut and ExecutionContext::handle_errors have been updated.
	### Added
	- *(executor)* normalize flatten errors for the final response ([#454](https://github.com/graphql-hive/router/pull/454))

[github-actions]

✅ k6-benchmark results

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

     █ setup

     checks.........................: 100.00% ✓ 228087      ✗ 0    
     data_received..................: 6.7 GB  222 MB/s
     data_sent......................: 89 MB   3.0 MB/s
     http_req_blocked...............: avg=3.86µs   min=722ns   med=1.86µs  max=11.42ms  p(90)=2.66µs  p(95)=3.04µs  
     http_req_connecting............: avg=1.14µs   min=0s      med=0s      max=3.65ms   p(90)=0s      p(95)=0s      
     http_req_duration..............: avg=19.26ms  min=2.08ms  med=18.38ms max=135.21ms p(90)=26.32ms p(95)=29.35ms 
       { expected_response:true }...: avg=19.26ms  min=2.08ms  med=18.38ms max=135.21ms p(90)=26.32ms p(95)=29.35ms 
     http_req_failed................: 0.00%   ✓ 0           ✗ 76049
     http_req_receiving.............: avg=132.86µs min=25.38µs med=41.54µs max=85.12ms  p(90)=87.12µs p(95)=370.18µs
     http_req_sending...............: avg=25.27µs  min=5.63µs  med=10.89µs max=19.74ms  p(90)=16.78µs p(95)=29.59µs 
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s      max=0s       p(90)=0s      p(95)=0s      
     http_req_waiting...............: avg=19.1ms   min=2.02ms  med=18.25ms max=96.31ms  p(90)=26.08ms p(95)=29.05ms 
     http_reqs......................: 76049   2529.561066/s
     iteration_duration.............: avg=19.72ms  min=4.44ms  med=18.73ms max=218.12ms p(90)=26.79ms p(95)=29.87ms 
     iterations.....................: 76029   2528.895821/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-476 ghcr.io/graphql-hive/router:sha-165c9da

Docker metadata

{
"buildx.build.ref": "builder-1b59d217-d110-482b-bc39-5fd17a4da85b/builder-1b59d217-d110-482b-bc39-5fd17a4da85b0/2g0g4rbo3g2b50zmbgub6skca",
"containerimage.descriptor": {
  "mediaType": "application/vnd.oci.image.index.v1+json",
  "digest": "sha256:40606ded41d120ef924ba6e48ffccbf461adae37c7ed26690fb8149c7b7aef02",
  "size": 1609
},
"containerimage.digest": "sha256:40606ded41d120ef924ba6e48ffccbf461adae37c7ed26690fb8149c7b7aef02",
"image.name": "ghcr.io/graphql-hive/router:pr-476,ghcr.io/graphql-hive/router:sha-165c9da"
}