chore(release): changelog for 1.2.0

Author: apollo-bot2

.changesets/feat_telemetry_metadata_headers_config_options.md

@@ -4,6 +4,49 @@ All notable changes to this project will be documented in this file.
 
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+# [1.2.0] - 2025-11-13
+
+## 🚀 Features
+
+### Adding config option to specify metadata/header values for telemetry exporters - @alocay PR #460
+
+Adding a `metadata` (for `grpc` protocol) and `headers` (for `http/protobuf` protocol) config option for the `telemetry.exporters.metrics.otlp` yaml config section.
+
+```yaml
+telemetry:
+  exporters:
+    metrics:
+      otlp:
+        endpoint: "http://127.0.0.1:4317"
+        protocol: "grpc"
+        metadata:
+          the-key: some-value
+    tracing:
+      otlp:
+        endpoint: "http://127.0.0.1:4317"
+        protocol: "http/protobuf"
+        headers:
+          some-key: another-value
+```
+
+## 🐛 Fixes
+
+### Allow using builtin names for custom tools - @dylan-apollo PR #481
+
+Previously, the names of builtin tools were reserved even if the tool was disabled.
+These names are now available for custom tools _if_ the matching builtin tool is disabled via config:
+- `introspect`
+- `search`
+- `explorer`
+- `execute`
+- `validate`
+
+### Improved performance of parallel tool calls - @dylan-apollo PR #475
+
+Responsiveness of all tools is improved when many clients are connected.
+
+
+
 # [1.1.1] - 2025-10-21
 
 ## 🐛 Fixes

.changesets/fix_allow-using-builtin-names-for-custom-tools.md

@@ -1,74 +1,41 @@
-# [1.1.0] - 2025-10-16
-
-## ❗ BREAKING ❗
-
-### Change default port from 5000 to 8000 - @DaleSeo PR #417
-
-The default server port has been changed from `5000` to `8000` to avoid conflicts with common development tools and services that typically use port 5000 (such as macOS AirPlay, Flask development servers, and other local services).
-
-**Migration**: If you were relying on the default port 5000, you can continue using it by explicitly setting the port in your configuration file or command line arguments.
-
-- Before 
-
-```yaml
-transport:
-  type: streamable_http
-```
-
-- After
-
-```yaml
-transport:
-  type: streamable_http
-  port: 5000
-```
+# [1.2.0] - 2025-11-13
 
 ## 🚀 Features
 
-### feat: Add configuration option for metric temporality - @swcollard PR #413
+### Adding config option to specify metadata/header values for telemetry exporters - @alocay PR #460
 
-Creates a new configuration option for telemetry to set the Metric temporality to either Cumulative (default) or Delta.
-
-* Cumulative - The metric value will be the overall value since the start of the measurement.
-* Delta - The metric will be the difference in the measurement since the last time it was reported.
-
-Some observability  vendors require that one is used over the other so we want to support the configuration in the MCP Server.
-
-### Add support for forwarding headers from MCP clients to GraphQL APIs - @DaleSeo PR #428
-
-Adds opt-in support for dynamic header forwarding, which enables metadata for A/B testing, feature flagging, geo information from CDNs, or internal instrumentation to be sent from MCP clients to downstream GraphQL APIs. It automatically blocks hop-by-hop headers according to the guidelines in [RFC 7230, section 6.1](https://datatracker.ietf.org/doc/html/rfc7230#section-6.1), and it only works with the Streamable HTTP transport.
-
-You can configure using the `forward_headers` setting:
+Adding a `metadata` (for `grpc` protocol) and `headers` (for `http/protobuf` protocol) config option for the `telemetry.exporters.metrics.otlp` yaml config section.
 
 ```yaml
-forward_headers:
-  - x-tenant-id
-  - x-experiment-id
-  - x-geo-country
+telemetry:
+  exporters:
+    metrics:
+      otlp:
+        endpoint: "http://127.0.0.1:4317"
+        protocol: "grpc"
+        metadata:
+          the-key: some-value
+    tracing:
+      otlp:
+        endpoint: "http://127.0.0.1:4317"
+        protocol: "http/protobuf"
+        headers:
+          some-key: another-value
 ```
 
-Please note that this feature is not intended for passing through credentials as documented in the best practices page.
-
-### feat: Add mcp-session-id header to HTTP request trace attributes - @swcollard PR #421
-
-Includes the value of the [Mcp-Session-Id](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#session-management) HTTP header as an attribute of the trace for HTTP requests to the MCP Server
-
 ## 🐛 Fixes
 
-### Fix compatibility issue with VSCode/Copilot - @DaleSeo PR #447
-
-This updates Apollo MCP Server’s tool schemas from [Draft 2020-12](https://json-schema.org/draft/2020-12) to [Draft‑07](https://json-schema.org/draft-07) which is more widely supported across different validators. VSCode/Copilot still validate against Draft‑07, so rejects Apollo MCP Server’s tools. Our JSON schemas don’t rely on newer features, so downgrading improves compatibility across MCP clients with no practical impact.
-
-## 🛠 Maintenance
-
-### Update rmcp sdk to version 0.8.x - @swcollard PR #433 
-
-Bumping the Rust MCP SDK version used in this server up to 0.8.x
+### Allow using builtin names for custom tools - @dylan-apollo PR #481
 
-### chore: Only initialize a single HTTP client for graphql requests - @swcollard PR #412
+Previously, the names of builtin tools were reserved even if the tool was disabled.
+These names are now available for custom tools _if_ the matching builtin tool is disabled via config:
+- `introspect`
+- `search`
+- `explorer`
+- `execute`
+- `validate`
 
-Currently the MCP Server spins up a new HTTP client every time it wants to make a request to the downstream graphql endpoint. This change creates a static reqwest client that gets initialized using LazyLock and reused on each graphql request.
+### Improved performance of parallel tool calls - @dylan-apollo PR #475
 
-This change is based on the suggestion from the reqwest [documentation](https://docs.rs/reqwest/latest/reqwest/struct.Client.html)
-> "The Client holds a connection pool internally, so it is advised that you create one and reuse it."
+Responsiveness of all tools is improved when many clients are connected.