chore(release): router crates and artifacts (#688)

> [!IMPORTANT]
> Merging this pull request will create these releases

# executor 6.3.5 (2026-01-22)
## Fixes

### New Query Complexity Configuration in `hive-router` and
`hive-router-config`

We have introduced a new configuration module for query complexity in
the Hive Router.

This includes new validation rules to enforce maximum query depth,
maximum number of directives in the incoming GraphQL operation, helping
to prevent overly complex queries that could impact performance.

## Max Depth

By default, it is disabled, but you can enable and configure it in your
router configuration as follows:

```yaml
limits:
  max_depth:
    n: 10  # Set the maximum allowed depth for queries
```

This configuration allows you to set a maximum depth for incoming
GraphQL queries, enhancing the robustness of your API by mitigating the
risk of deep-nested queries.

## Max Directives

You can also limit the number of directives in incoming GraphQL
operations. This is also disabled by default. You can enable and
configure it as follows:

```yaml
limits:
  max_directives:
    n: 5  # Set the maximum allowed number of directives
```

This configuration helps to prevent excessive use of directives in
queries, which can lead to performance issues.

## Max Tokens

Additionally, we have introduced a new configuration option to limit the
maximum number of tokens in incoming GraphQL operations. This feature is
designed to prevent excessively large queries that could impact server
performance.

By default, this limit is disabled. You can enable and configure it in
your router configuration as follows:

```yaml
limits:
  max_tokens:
    n: 1000  # Set the maximum allowed number of tokens
```

This configuration allows you to set a maximum token count for incoming
GraphQL queries, helping to ensure that queries remain manageable and do
not overwhelm the server.

With these new configurations, you can better manage the complexity of
incoming GraphQL queries and ensure the stability and performance of
your API.

### Refactor Parse Error Handling in `graphql-tools`

Breaking;
- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
- - So that the internals of the error can be better structured and more
informative, such as including line and column information.
- `ParseError`s are no longer prefixed with "query parse error: " in
their Display implementation.
# query-planner 2.1.7 (2026-01-22)
## Fixes

### Refactor Parse Error Handling in `graphql-tools`

Breaking;
- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
- - So that the internals of the error can be better structured and more
informative, such as including line and column information.
- `ParseError`s are no longer prefixed with "query parse error: " in
their Display implementation.
# config 0.0.18 (2026-01-22)
## Features

### New Query Complexity Configuration in `hive-router` and
`hive-router-config`

We have introduced a new configuration module for query complexity in
the Hive Router.

This includes new validation rules to enforce maximum query depth,
maximum number of directives in the incoming GraphQL operation, helping
to prevent overly complex queries that could impact performance.

## Max Depth

By default, it is disabled, but you can enable and configure it in your
router configuration as follows:

```yaml
limits:
  max_depth:
    n: 10  # Set the maximum allowed depth for queries
```

This configuration allows you to set a maximum depth for incoming
GraphQL queries, enhancing the robustness of your API by mitigating the
risk of deep-nested queries.

## Max Directives

You can also limit the number of directives in incoming GraphQL
operations. This is also disabled by default. You can enable and
configure it as follows:

```yaml
limits:
  max_directives:
    n: 5  # Set the maximum allowed number of directives
```

This configuration helps to prevent excessive use of directives in
queries, which can lead to performance issues.

## Max Tokens

Additionally, we have introduced a new configuration option to limit the
maximum number of tokens in incoming GraphQL operations. This feature is
designed to prevent excessively large queries that could impact server
performance.

By default, this limit is disabled. You can enable and configure it in
your router configuration as follows:

```yaml
limits:
  max_tokens:
    n: 1000  # Set the maximum allowed number of tokens
```

This configuration allows you to set a maximum token count for incoming
GraphQL queries, helping to ensure that queries remain manageable and do
not overwhelm the server.

With these new configurations, you can better manage the complexity of
incoming GraphQL queries and ensure the stability and performance of
your API.
# hive-console-sdk 0.3.4 (2026-01-22)
## Fixes

### Refactor Parse Error Handling in `graphql-tools`

Breaking;
- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
- - So that the internals of the error can be better structured and more
informative, such as including line and column information.
- `ParseError`s are no longer prefixed with "query parse error: " in
their Display implementation.
# node-addon 0.0.11 (2026-01-22)
## Fixes

### Refactor Parse Error Handling in `graphql-tools`

Breaking;
- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
- - So that the internals of the error can be better structured and more
informative, such as including line and column information.
- `ParseError`s are no longer prefixed with "query parse error: " in
their Display implementation.
# graphql-tools 0.5.0 (2026-01-22)
## Breaking Changes

### Refactor Parse Error Handling in `graphql-tools`

Breaking;
- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
- - So that the internals of the error can be better structured and more
informative, such as including line and column information.
- `ParseError`s are no longer prefixed with "query parse error: " in
their Display implementation.
# internal 0.0.7 (2026-01-22)
## Fixes

### New Query Complexity Configuration in `hive-router` and
`hive-router-config`

We have introduced a new configuration module for query complexity in
the Hive Router.

This includes new validation rules to enforce maximum query depth,
maximum number of directives in the incoming GraphQL operation, helping
to prevent overly complex queries that could impact performance.

## Max Depth

By default, it is disabled, but you can enable and configure it in your
router configuration as follows:

```yaml
limits:
  max_depth:
    n: 10  # Set the maximum allowed depth for queries
```

This configuration allows you to set a maximum depth for incoming
GraphQL queries, enhancing the robustness of your API by mitigating the
risk of deep-nested queries.

## Max Directives

You can also limit the number of directives in incoming GraphQL
operations. This is also disabled by default. You can enable and
configure it as follows:

```yaml
limits:
  max_directives:
    n: 5  # Set the maximum allowed number of directives
```

This configuration helps to prevent excessive use of directives in
queries, which can lead to performance issues.

## Max Tokens

Additionally, we have introduced a new configuration option to limit the
maximum number of tokens in incoming GraphQL operations. This feature is
designed to prevent excessively large queries that could impact server
performance.

By default, this limit is disabled. You can enable and configure it in
your router configuration as follows:

```yaml
limits:
  max_tokens:
    n: 1000  # Set the maximum allowed number of tokens
```

This configuration allows you to set a maximum token count for incoming
GraphQL queries, helping to ensure that queries remain manageable and do
not overwhelm the server.

With these new configurations, you can better manage the complexity of
incoming GraphQL queries and ensure the stability and performance of
your API.
# router 0.0.33 (2026-01-22)
## Features

- Query Complexity: Max Depth, Max Directives, Max Tokens (#623)
- Enable/Disable Introspection with `introspection` (#655)

### New Query Complexity Configuration in `hive-router` and
`hive-router-config`

We have introduced a new configuration module for query complexity in
the Hive Router.

This includes new validation rules to enforce maximum query depth,
maximum number of directives in the incoming GraphQL operation, helping
to prevent overly complex queries that could impact performance.

## Max Depth

By default, it is disabled, but you can enable and configure it in your
router configuration as follows:

```yaml
limits:
  max_depth:
    n: 10  # Set the maximum allowed depth for queries
```

This configuration allows you to set a maximum depth for incoming
GraphQL queries, enhancing the robustness of your API by mitigating the
risk of deep-nested queries.

## Max Directives

You can also limit the number of directives in incoming GraphQL
operations. This is also disabled by default. You can enable and
configure it as follows:

```yaml
limits:
  max_directives:
    n: 5  # Set the maximum allowed number of directives
```

This configuration helps to prevent excessive use of directives in
queries, which can lead to performance issues.

## Max Tokens

Additionally, we have introduced a new configuration option to limit the
maximum number of tokens in incoming GraphQL operations. This feature is
designed to prevent excessively large queries that could impact server
performance.

By default, this limit is disabled. You can enable and configure it in
your router configuration as follows:

```yaml
limits:
  max_tokens:
    n: 1000  # Set the maximum allowed number of tokens
```

This configuration allows you to set a maximum token count for incoming
GraphQL queries, helping to ensure that queries remain manageable and do
not overwhelm the server.

With these new configurations, you can better manage the complexity of
incoming GraphQL queries and ensure the stability and performance of
your API.

### Refactor Router Initialization Error Handling in `hive-router`

- New `RouterInitError` enum to represent initialization errors in the
Hive Router.
- `router_entrypoint` now returns `Result<(), RouterInitError>` instead
of a boxed dynamic error(`Box<dyn std::error::Error>`), providing more
specific error handling during router initialization.

## Fixes

- Expose query plan with option "dry-run" wont execute the query plan

### Refactor Parse Error Handling in `graphql-tools`

Breaking;
- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
- - So that the internals of the error can be better structured and more
informative, such as including line and column information.
- `ParseError`s are no longer prefixed with "query parse error: " in
their Display implementation.

Co-authored-by: knope-bot[bot] <152252888+knope-bot[bot]@users.noreply.github.com>

Author: knope-bot[bot]

.changeset/expose_query_plan_with_option_dry_run_wont_execute_the_query_plan.md

@@ -116,6 +116,75 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Other
 
 - *(deps)* update release-plz/action action to v0.5.113 ([#389](https://github.com/graphql-hive/router/pull/389))
+## 0.0.33 (2026-01-22)
+
+### Features
+
+- Query Complexity: Max Depth, Max Directives, Max Tokens (#623)
+- Enable/Disable Introspection with `introspection` (#655)
+
+#### New Query Complexity Configuration in `hive-router` and `hive-router-config`
+
+We have introduced a new configuration module for query complexity in the Hive Router. 
+
+This includes new validation rules to enforce maximum query depth, maximum number of directives in the incoming GraphQL operation, helping to prevent overly complex queries that could impact performance.
+
+### Max Depth
+
+By default, it is disabled, but you can enable and configure it in your router configuration as follows:
+
+```yaml
+limits:
+  max_depth:
+    n: 10  # Set the maximum allowed depth for queries
+```
+
+This configuration allows you to set a maximum depth for incoming GraphQL queries, enhancing the robustness of your API by mitigating the risk of deep-nested queries.
+
+### Max Directives
+
+You can also limit the number of directives in incoming GraphQL operations. This is also disabled by default. You can enable and configure it as follows:
+
+```yaml
+limits:
+  max_directives:
+    n: 5  # Set the maximum allowed number of directives
+```
+
+This configuration helps to prevent excessive use of directives in queries, which can lead to performance issues.
+
+### Max Tokens
+
+Additionally, we have introduced a new configuration option to limit the maximum number of tokens in incoming GraphQL operations. This feature is designed to prevent excessively large queries that could impact server performance.
+
+By default, this limit is disabled. You can enable and configure it in your router configuration as follows:
+
+```yaml
+limits:
+  max_tokens:
+    n: 1000  # Set the maximum allowed number of tokens
+```
+
+This configuration allows you to set a maximum token count for incoming GraphQL queries, helping to ensure that queries remain manageable and do not overwhelm the server.
+
+With these new configurations, you can better manage the complexity of incoming GraphQL queries and ensure the stability and performance of your API.
+
+#### Refactor Router Initialization Error Handling in `hive-router`
+
+- New `RouterInitError` enum to represent initialization errors in the Hive Router.
+- `router_entrypoint` now returns `Result<(), RouterInitError>` instead of a boxed dynamic error(`Box<dyn std::error::Error>`), providing more specific error handling during router initialization.
+
+### Fixes
+
+- Expose query plan with option "dry-run" wont execute the query plan
+
+#### Refactor Parse Error Handling in `graphql-tools`
+
+Breaking;
+- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
+- - So that the internals of the error can be better structured and more informative, such as including line and column information.
+- `ParseError`s are no longer prefixed with "query parse error: " in their Display implementation.
+
 ## 0.0.32 (2026-01-16)
 
 ### Fixes

.changeset/query_complexity.md

@@ -1,6 +1,6 @@
 [package]
 name = "hive-router"
-version = "0.0.32"
+version = "0.0.33"
 edition = "2021"
 description = "GraphQL router/gateway for Federation"
 license = "MIT"
@@ -16,12 +16,12 @@ name = "hive_router"
 path = "src/main.rs"
 
 [dependencies]
-hive-router-query-planner = { path = "../../lib/query-planner", version = "2.1.6" }
-hive-router-plan-executor = { path = "../../lib/executor", version = "6.3.4" }
-hive-router-config = { path = "../../lib/router-config", version = "0.0.17" }
-hive-router-internal = { path = "../../lib/internal", version = "0.0.6" }
-hive-console-sdk = { path = "../../lib/hive-console-sdk", version = "0.3.3" }
-graphql-tools =  { path = "../../lib/graphql-tools", version = "0.4.2" }
+hive-router-query-planner = { path = "../../lib/query-planner", version = "2.1.7" }
+hive-router-plan-executor = { path = "../../lib/executor", version = "6.3.5" }
+hive-router-config = { path = "../../lib/router-config", version = "0.0.18" }
+hive-router-internal = { path = "../../lib/internal", version = "0.0.7" }
+hive-console-sdk = { path = "../../lib/hive-console-sdk", version = "0.3.4" }
+graphql-tools =  { path = "../../lib/graphql-tools", version = "0.5.0" }
 
 tokio = { workspace = true }
 futures = { workspace = true }

.changeset/refactor_init_error.md

@@ -94,6 +94,63 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Other
 
 - *(deps)* update release-plz/action action to v0.5.113 ([#389](https://github.com/graphql-hive/router/pull/389))
+## 6.3.5 (2026-01-22)
+
+### Fixes
+
+#### New Query Complexity Configuration in `hive-router` and `hive-router-config`
+
+We have introduced a new configuration module for query complexity in the Hive Router. 
+
+This includes new validation rules to enforce maximum query depth, maximum number of directives in the incoming GraphQL operation, helping to prevent overly complex queries that could impact performance.
+
+### Max Depth
+
+By default, it is disabled, but you can enable and configure it in your router configuration as follows:
+
+```yaml
+limits:
+  max_depth:
+    n: 10  # Set the maximum allowed depth for queries
+```
+
+This configuration allows you to set a maximum depth for incoming GraphQL queries, enhancing the robustness of your API by mitigating the risk of deep-nested queries.
+
+### Max Directives
+
+You can also limit the number of directives in incoming GraphQL operations. This is also disabled by default. You can enable and configure it as follows:
+
+```yaml
+limits:
+  max_directives:
+    n: 5  # Set the maximum allowed number of directives
+```
+
+This configuration helps to prevent excessive use of directives in queries, which can lead to performance issues.
+
+### Max Tokens
+
+Additionally, we have introduced a new configuration option to limit the maximum number of tokens in incoming GraphQL operations. This feature is designed to prevent excessively large queries that could impact server performance.
+
+By default, this limit is disabled. You can enable and configure it in your router configuration as follows:
+
+```yaml
+limits:
+  max_tokens:
+    n: 1000  # Set the maximum allowed number of tokens
+```
+
+This configuration allows you to set a maximum token count for incoming GraphQL queries, helping to ensure that queries remain manageable and do not overwhelm the server.
+
+With these new configurations, you can better manage the complexity of incoming GraphQL queries and ensure the stability and performance of your API.
+
+#### Refactor Parse Error Handling in `graphql-tools`
+
+Breaking;
+- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
+- - So that the internals of the error can be better structured and more informative, such as including line and column information.
+- `ParseError`s are no longer prefixed with "query parse error: " in their Display implementation.
+
 ## 6.3.4 (2026-01-16)
 
 ### Fixes

.changeset/refactor_parse_error.md

@@ -1,6 +1,6 @@
 [package]
 name = "hive-router-plan-executor"
-version = "6.3.4"
+version = "6.3.5"
 edition = "2021"
 description = "GraphQL query planner executor for Federation specification"
 license = "MIT"
@@ -12,10 +12,10 @@ authors = ["The Guild"]
 [lib]
 
 [dependencies]
-hive-router-query-planner = { path = "../query-planner", version = "2.1.6" }
-hive-router-config = { path = "../router-config", version = "0.0.17" }
-hive-router-internal = { path = "../internal", version = "0.0.6" }
-graphql-tools =  { path = "../graphql-tools", version = "0.4.2" }
+hive-router-query-planner = { path = "../query-planner", version = "2.1.7" }
+hive-router-config = { path = "../router-config", version = "0.0.18" }
+hive-router-internal = { path = "../internal", version = "0.0.7" }
+graphql-tools =  { path = "../graphql-tools", version = "0.5.0" }
 
 async-trait = { workspace = true }
 futures = { workspace = true }

Cargo.lock

@@ -1,3 +1,14 @@
+## 0.5.0 (2026-01-22)
+
+### Breaking Changes
+
+#### Refactor Parse Error Handling in `graphql-tools`
+
+Breaking;
+- `ParseError(String)` is now `ParseError(InternalError<'static>)`.
+- - So that the internals of the error can be better structured and more informative, such as including line and column information.
+- `ParseError`s are no longer prefixed with "query parse error: " in their Display implementation.
+
 ## 0.4.2 (2026-01-16)
 
 ### Fixes