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

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

# router 0.0.21 (2025-11-28)
## Features

- Subgraph Timeout Configuration (#541)

### Subgraph Request Timeout Feature

Adds support for configurable subgraph request timeouts via the
`traffic_shaping` configuration. The `request_timeout` option allows you
to specify the maximum time the router will wait for a response from a
subgraph before timing out the request. You can set a static timeout
(e.g., `30s`) globally or per-subgraph, or use dynamic timeouts with VRL
expressions to vary timeout values based on request characteristics.
This helps protect your router from hanging requests and enables
fine-grained control over how long requests to different subgraphs
should be allowed to run.

### Rename `original_url` variable to `default` in subgraph URL override
expressions.

This change aligns the variable naming with other configuration
expressions, such as timeout configuration.

When using expressions to override subgraph URLs, use `.default` to
refer to the original URL defined in the subgraph definition.

Example:

```yaml
url:
  expression: |
    if .request.headers."x-region" == "us-east" {
      "https://products-us-east.example.com/graphql"
    } else {
      .default
    }
```

## Fixes

- support `@include` and `@skip` in initial fetch node (#591)
- Fixed an issue where `@skip` and `@include` directives were
incorrectly removed from the initial Fetch of the Query Plan.
# node-addon 0.0.5 (2025-11-28)
## Fixes

- support `@include` and `@skip` in initial fetch node (#591)
- Fixed an issue where `@skip` and `@include` directives were
incorrectly removed from the initial Fetch of the Query Plan.
# query-planner 2.1.1 (2025-11-28)
## Fixes

- support `@include` and `@skip` in initial fetch node (#591)
- Fixed an issue where `@skip` and `@include` directives were
incorrectly removed from the initial Fetch of the Query Plan.
# config 0.0.13 (2025-11-28)
## Features

### Subgraph Request Timeout Feature

Adds support for configurable subgraph request timeouts via the
`traffic_shaping` configuration. The `request_timeout` option allows you
to specify the maximum time the router will wait for a response from a
subgraph before timing out the request. You can set a static timeout
(e.g., `30s`) globally or per-subgraph, or use dynamic timeouts with VRL
expressions to vary timeout values based on request characteristics.
This helps protect your router from hanging requests and enables
fine-grained control over how long requests to different subgraphs
should be allowed to run.

### Rename `original_url` variable to `default` in subgraph URL override
expressions.

This change aligns the variable naming with other configuration
expressions, such as timeout configuration.

When using expressions to override subgraph URLs, use `.default` to
refer to the original URL defined in the subgraph definition.

Example:

```yaml
url:
  expression: |
    if .request.headers."x-region" == "us-east" {
      "https://products-us-east.example.com/graphql"
    } else {
      .default
    }
```

## Fixes

- support `@include` and `@skip` in initial fetch node (#591)
# executor 6.2.0 (2025-11-28)
## Features

### Subgraph Request Timeout Feature

Adds support for configurable subgraph request timeouts via the
`traffic_shaping` configuration. The `request_timeout` option allows you
to specify the maximum time the router will wait for a response from a
subgraph before timing out the request. You can set a static timeout
(e.g., `30s`) globally or per-subgraph, or use dynamic timeouts with VRL
expressions to vary timeout values based on request characteristics.
This helps protect your router from hanging requests and enables
fine-grained control over how long requests to different subgraphs
should be allowed to run.

### Rename `original_url` variable to `default` in subgraph URL override
expressions.

This change aligns the variable naming with other configuration
expressions, such as timeout configuration.

When using expressions to override subgraph URLs, use `.default` to
refer to the original URL defined in the subgraph definition.

Example:

```yaml
url:
  expression: |
    if .request.headers."x-region" == "us-east" {
      "https://products-us-east.example.com/graphql"
    } else {
      .default
    }
```

## Fixes

- support `@include` and `@skip` in initial fetch node (#591)

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

Author: knope-bot[bot]

.changeset/asd.md

@@ -116,6 +116,39 @@ 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.21 (2025-11-28)
+
+### Features
+
+- Subgraph Timeout Configuration (#541)
+
+#### Subgraph Request Timeout Feature
+
+Adds support for configurable subgraph request timeouts via the `traffic_shaping` configuration. The `request_timeout` option allows you to specify the maximum time the router will wait for a response from a subgraph before timing out the request. You can set a static timeout (e.g., `30s`) globally or per-subgraph, or use dynamic timeouts with VRL expressions to vary timeout values based on request characteristics. This helps protect your router from hanging requests and enables fine-grained control over how long requests to different subgraphs should be allowed to run.
+
+#### Rename `original_url` variable to `default` in subgraph URL override expressions.
+
+This change aligns the variable naming with other configuration expressions, such as timeout configuration.
+
+When using expressions to override subgraph URLs, use `.default` to refer to the original URL defined in the subgraph definition.
+
+Example:
+
+```yaml
+url:
+  expression: |
+    if .request.headers."x-region" == "us-east" {
+      "https://products-us-east.example.com/graphql"
+    } else {
+      .default
+    }
+```
+
+### Fixes
+
+- support `@include` and `@skip` in initial fetch node (#591)
+- Fixed an issue where `@skip` and `@include` directives were incorrectly removed from the initial Fetch of the Query Plan.
+
 ## 0.0.20 (2025-11-24)
 
 ### Features

.changeset/fix-cond.md

@@ -1,6 +1,6 @@
 [package]
 name = "hive-router"
-version = "0.0.20"
+version = "0.0.21"
 edition = "2021"
 description = "GraphQL router/gateway for Federation"
 license = "MIT"
@@ -16,9 +16,9 @@ name = "hive_router"
 path = "src/main.rs"
 
 [dependencies]
-hive-router-query-planner = { path = "../../lib/query-planner", version = "2.1.0" }
-hive-router-plan-executor = { path = "../../lib/executor", version = "6.1.0" }
-hive-router-config = { path = "../../lib/router-config", version = "0.0.12" }
+hive-router-query-planner = { path = "../../lib/query-planner", version = "2.1.1" }
+hive-router-plan-executor = { path = "../../lib/executor", version = "6.2.0" }
+hive-router-config = { path = "../../lib/router-config", version = "0.0.13" }
 
 tokio = { workspace = true }
 futures = { workspace = true }

.changeset/rename_original_url_variable_to_default_in_subgraph_url_override_expressions.md

@@ -94,6 +94,36 @@ 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.2.0 (2025-11-28)
+
+### Features
+
+#### Subgraph Request Timeout Feature
+
+Adds support for configurable subgraph request timeouts via the `traffic_shaping` configuration. The `request_timeout` option allows you to specify the maximum time the router will wait for a response from a subgraph before timing out the request. You can set a static timeout (e.g., `30s`) globally or per-subgraph, or use dynamic timeouts with VRL expressions to vary timeout values based on request characteristics. This helps protect your router from hanging requests and enables fine-grained control over how long requests to different subgraphs should be allowed to run.
+
+#### Rename `original_url` variable to `default` in subgraph URL override expressions.
+
+This change aligns the variable naming with other configuration expressions, such as timeout configuration.
+
+When using expressions to override subgraph URLs, use `.default` to refer to the original URL defined in the subgraph definition.
+
+Example:
+
+```yaml
+url:
+  expression: |
+    if .request.headers."x-region" == "us-east" {
+      "https://products-us-east.example.com/graphql"
+    } else {
+      .default
+    }
+```
+
+### Fixes
+
+- support `@include` and `@skip` in initial fetch node (#591)
+
 ## 6.1.0 (2025-11-24)
 
 ### Features

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "hive-router-plan-executor"
-version = "6.1.0"
+version = "6.2.0"
 edition = "2021"
 description = "GraphQL query planner executor for Federation specification"
 license = "MIT"
@@ -12,8 +12,8 @@ authors = ["The Guild"]
 [lib]
 
 [dependencies]
-hive-router-query-planner = { path = "../query-planner", version = "2.1.0" }
-hive-router-config = { path = "../router-config", version = "0.0.12" }
+hive-router-query-planner = { path = "../query-planner", version = "2.1.1" }
+hive-router-config = { path = "../router-config", version = "0.0.13" }
 
 graphql-parser = { workspace = true }
 graphql-tools = { workspace = true }

bin/router/CHANGELOG.md

@@ -1,4 +1,11 @@
 # @graphql-hive/router-query-planner changelog
+## 0.0.5 (2025-11-28)
+
+### Fixes
+
+- support `@include` and `@skip` in initial fetch node (#591)
+- Fixed an issue where `@skip` and `@include` directives were incorrectly removed from the initial Fetch of the Query Plan.
+
 ## 0.0.4 (2025-11-24)
 
 ### Fixes

bin/router/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 edition = "2021"
-version = "0.0.4"
+version = "0.0.5"
 name = "node-addon"
 publish = false