release: v0.9.0-rc.0 (#1003)

CHANGELOG.md

@@ -4,6 +4,106 @@ All notable changes to Router will be documented in this file.
 
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+# [v0.9.0-rc.0] - 2022-05-10
+## ❗ BREAKING ❗
+
+### Env variables naming [PR #990](https://github.com/apollographql/router/pull/990) [PR #992](https://github.com/apollographql/router/pull/992)
+Environment variables have been renamed for consistency:
+* `RUST_LOG` -> `APOLLO_ROUTER_LOG`
+* `CONFIGURATION_PATH` -> `APOLLO_ROUTER_CONFIG_PATH`
+* `SUPERGRAPH_PATH` -> `APOLLO_ROUTER_SUPERGRAPH_PATH`
+* `ROUTER_HOT_RELOAD` -> `APOLLO_ROUTER_HOT_RELOAD`
+* `APOLLO_SCHEMA_CONFIG_DELIVERY_ENDPOINT` -> `APOLLO_UPLINK_ENDPOINTS`
+* `APOLLO_SCHEMA_POLL_INTERVAL`-> `APOLLO_UPLINK_INTERVAL`
+
+In addition, the following command line flags have changed:
+* `--apollo-schema-config-delivery-endpoint` -> `--apollo-uplink-url`
+* `--apollo-schema-poll-interval` -> `--apollo-uplink-poll-interval`
+
+### Add configuration to declare your own GraphQL endpoint [PR #976](https://github.com/apollographql/router/pull/976)
+You are now able to declare your own GraphQL endpoint in the config like this:
+```yaml
+server:
+  # The socket address and port to listen on
+  # Defaults to 127.0.0.1:4000
+  listen: 127.0.0.1:4000
+  # Default is /
+  endpoint: /graphql
+```
+But we also deleted the `/graphql` endpoint by default, you will know have only one existing GraphQL endpoint and by default it's `/`. If you need to use `/graphql` instead then refer to my previous example.
+
+### rhai scripts should be able to do more things (like rust plugins) [PR #971](https://github.com/apollographql/router/pull/971)
+This is a re-working of our rhai scripting support. The intent is to make writing a rhai plugin more like writing a rust plugin, with full participation in the service plugin lifecycle. The work is still some way from complete, but does provide new capabilities (such as logging from rhai) and provides a more solid basis on which we can evolve our implementation. The examples and documentation should make clear how to modify any existing scripts to accomodate the changes.
+
+## 🚀 Features ( :rocket: )
+
+### Panics now output to logs [PR #1001](https://github.com/apollographql/router/pull/1001) [PR #1004](https://github.com/apollographql/router/pull/1004)
+Previously panics would get swallowed. Now they are output to the logs.
+Setting `RUST_BACKTRACE=1` or `RUST_BACKTRACE=full` enables the full backtrace to also be logged.
+
+### Apollo studio Usage Reporting [PR #898](https://github.com/apollographql/router/pull/898)
+If you have [enabled telemetry](https://www.apollographql.com/docs/router/configuration/apollo-telemetry#enabling-usage-reporting), you can now see field usage reporting for your queries by heading to the Apollo studio fields section.
+Here is more information on how to [set up telemetry](https://www.apollographql.com/docs/studio/metrics/usage-reporting#pushing-metrics-from-apollo-server) and [Field Usage](https://www.apollographql.com/docs/studio/metrics/field-usage)
+
+### PluginTestHarness [PR #898](https://github.com/apollographql/router/pull/898)
+Added a simple plugin test harness that can provide canned responses to queries. This harness is early in development and the functionality and APIs will probably change. 
+```rust
+ let mut test_harness = PluginTestHarness::builder()
+            .plugin(plugin)
+            .schema(Canned)
+            .build()
+            .await?;
+
+let _ = test_harness
+    .call(
+        RouterRequest::fake_builder()
+            .header("name_header", "test_client")
+            .header("version_header", "1.0-test")
+            .query(query)
+            .and_operation_name(operation_name)
+            .and_context(context)
+            .build()?,
+    )
+    .await;
+```
+## 🐛 Fixes ( :bug: )
+
+### Improve the configuration error report [PR #963](https://github.com/apollographql/router/pull/963)
+In case you have unknown properties on your configuration it will highlight the entity with unknown properties. Before we always pointed on the first field of this entity even if it wasn't the bad one, it's now fixed.
+
+### Only allow mutations on HTTP POST requests [PR #975](https://github.com/apollographql/router/pull/975)
+Mutations are now only accepted when using the HTTP POST method.
+
+### Fix incorrectly omitting content of interface's fragment [PR #949](https://github.com/apollographql/router/pull/949)
+Router now distinguish between fragment on concrete type and interface.
+If interface is encountered and  `__typename` is queried, additionally checks that returned type implements interface.
+
+### Set the service name if not specified in config or environment [PR #960](https://github.com/apollographql/router/pull/960)
+The router now sets "router" as default service name in Opentelemetry traces, that can be replaced using the configuration file or environment variables. It also sets the key "process.executable_name".
+
+### Accept an endpoint URL without scheme for telemetry [PR #964](https://github.com/apollographql/router/pull/964)
+
+Endpoint configuration for Datadog and OTLP take a URL as argument, but was incorrectly recognizing addresses of the format "host:port"
+
+### Stricter application of @inaccessible [PR #985](https://github.com/apollographql/router/pull/985)
+
+query-planner-js 2.0.2 implements stricter usage of the @inaccessible directive.
+
+### Impose recursion limits on selection processing [PR #995](https://github.com/apollographql/router/pull/995)
+
+this limits queries to a depth of 512.
+
+## 🛠 Maintenance ( :hammer_and_wrench: )
+
+### Use official SPDX license identifier for Elastic License v2 (ELv2) [Issue #418](https://github.com/apollographql/router/issues/418)
+
+Rather than pointing to our `LICENSE` file, we now use the `Elastic-2.0` SPDX license identifier to indicate that a particular component is governed by the Elastic License 2.0 (ELv2).  This should facilitate automated compatibility with licensing tools which assist with compliance.
+## 📚 Documentation ( :books: )
+
+### Add license notice to first line of Router output  [PR #986](https://github.com/apollographql/router/pull/986)
+Display the [ELv2 license](https://www.elastic.co/blog/elastic-license-v2) at the start of the Router
+
+
 # [v0.1.0-preview.7] - 2022-05-04
 ## ❗ BREAKING ❗
 

NEXT_CHANGELOG.md

@@ -17,99 +17,17 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## Example section entry format
 
-- **Headline** ([PR #PR_NUMBER](https://github.com/apollographql/router/pull/PR_NUMBER))
+### **Headline** ([PR #PR_NUMBER](https://github.com/apollographql/router/pull/PR_NUMBER))
 
-  Description! And a link to a [reference](http://url)
+Description! And a link to a [reference](http://url)
 -->
 
-# [v0.1.0-preview.8] - (unreleased)
+# [v0.9.0-rc.1] - (unreleased)
 ## ❗ BREAKING ❗
 
-### Env variables naming [PR #990](https://github.com/apollographql/router/pull/990)
-Environment variables have been renamed for consistency:
-* `RUST_LOG` -> `APOLLO_ROUTER_LOG`
-* `CONFIGURATION_PATH` -> `APOLLO_ROUTER_CONFIG_PATH`
-* `SUPERGRAPH_PATH` -> `APOLLO_ROUTER_SUPERGRAPH_PATH`
-* `ROUTER_HOT_RELOAD` -> `APOLLO_ROUTER_HOT_RELOAD`
-* `APOLLO_SCHEMA_CONFIG_DELIVERY_ENDPOINT` -> `APOLLO_UPLINK_ENDPOINTS`
-* `APOLLO_SCHEMA_POLL_INTERVAL`-> `APOLLO_UPLINK_INTERVAL`
-
-In addition, the following command line flags have changed:
-* `--apollo-schema-config-delivery-endpoint` -> `--apollo-uplink-url`
-* `--apollo-schema-poll-interval` -> `--apollo-uplink-poll-interval`
-
-### Add configuration to declare your own GraphQL endpoint [PR #976](https://github.com/apollographql/router/pull/976)
-You are now able to declare your own GraphQL endpoint in the config like this:
-```yaml
-server:
-  # The socket address and port to listen on
-  # Defaults to 127.0.0.1:4000
-  listen: 127.0.0.1:4000
-  # Default is /
-  endpoint: /graphql
-```
-But we also deleted the `/graphql` endpoint by default, you will know have only one existing GraphQL endpoint and by default it's `/`. If you need to use `/graphql` instead then refer to my previous example.
-
-### rhai scripts should be able to do more things (like rust plugins) [PR #971](https://github.com/apollographql/router/pull/971)
-This is a re-working of our rhai scripting support. The intent is to make writing a rhai plugin more like writing a rust plugin, with full participation in the service plugin lifecycle. The work is still some way from complete, but does provide new capabilities (such as logging from rhai) and provides a more solid basis on which we can evolve our implementation. The examples and documentation should make clear how to modify any existing scripts to accomodate the changes.
-
+## ❗ BREAKING ❗
 ## 🚀 Features ( :rocket: )
-
-### Panics now output to logs [PR #1001](https://github.com/apollographql/router/pull/1001) [PR #1004](https://github.com/apollographql/router/pull/1004)
-Previously panics would get swallowed. Now they are output to the logs.
-Setting `RUST_BACKTRACE=1` or `RUST_BACKTRACE=full` enables the full backtrace to also be logged.
-
-### Apollo studio Usage Reporting [PR #898](https://github.com/apollographql/router/pull/898)
-If you have [enabled telemetry](https://www.apollographql.com/docs/router/configuration/apollo-telemetry#enabling-usage-reporting), you can now see field usage reporting for your queries by heading to the Apollo studio fields section.
-Here is more information on how to [set up telemetry](https://www.apollographql.com/docs/studio/metrics/usage-reporting#pushing-metrics-from-apollo-server) and [Field Usage](https://www.apollographql.com/docs/studio/metrics/field-usage)
-
-### PluginTestHarness [PR #898](https://github.com/apollographql/router/pull/898)
-Added a simple plugin test harness that can provide canned responses to queries. This harness is early in development and the functionality and APIs will probably change. 
-```rust
- let mut test_harness = PluginTestHarness::builder()
-            .plugin(plugin)
-            .schema(Canned)
-            .build()
-            .await?;
-
-let _ = test_harness
-    .call(
-        RouterRequest::fake_builder()
-            .header("name_header", "test_client")
-            .header("version_header", "1.0-test")
-            .query(query)
-            .and_operation_name(operation_name)
-            .and_context(context)
-            .build()?,
-    )
-    .await;
-```
 ## 🐛 Fixes ( :bug: )
-
-### Improve the configuration error report [PR #963](https://github.com/apollographql/router/pull/963)
-In case you have unknown properties on your configuration it will highlight the entity with unknown properties. Before we always pointed on the first field of this entity even if it wasn't the bad one, it's now fixed.
-
-### Fix incorrectly omitting content of interface's fragment [PR #949](https://github.com/apollographql/router/pull/949)
-Router now distinguish between fragment on concrete type and interface.
-If interface is encountered and  `__typename` is queried, additionally checks that returned type implements interface.
-
-### Set the service name if not specified in config or environment [PR #960](https://github.com/apollographql/router/pull/960)
-The router now sets "router" as default service name in Opentelemetry traces, that can be replaced using the configuration file or environment variables. It also sets the key "process.executable_name".
-
-### Accept an endpoint URL without scheme for telemetry [PR #964](https://github.com/apollographql/router/pull/964)
-
-Endpoint configuration for Datadog and OTLP take a URL as argument, but was incorrectly recognizing addresses of the format "host:port"
-
-### Stricter application of @inaccessible [PR #985](https://github.com/apollographql/router/pull/985)
-
-query-planner-js 2.0.2 implements stricter usage of the @inaccessible directive.
-
 ## 🛠 Maintenance ( :hammer_and_wrench: )
-
-### Use official SPDX license identifier for Elastic License v2 (ELv2) [Issue #418](https://github.com/apollographql/router/issues/418)
-
-Rather than pointing to our `LICENSE` file, we now use the `Elastic-2.0` SPDX license identifier to indicate that a particular component is governed by the Elastic License 2.0 (ELv2).  This should facilitate automated compatibility with licensing tools which assist with compliance.
 ## 📚 Documentation ( :books: )
-
-### Add license notice to first line of Router output  [PR #986](https://github.com/apollographql/router/pull/986)
-Display the [ELv2 license](https://www.elastic.co/blog/elastic-license-v2) at the start of the Router
+## 🐛 Fixes ( :bug: )

RELEASE_CHECKLIST.md

@@ -36,13 +36,12 @@ in lieu of an official changelog.
 3. Update the version in `*/Cargo.toml`.
 4. Update the version in `NEXT_CHANGELOG.md`.
 5. Clear `NEXT_CHANGELOG.md` leaving only the template.
-6. Update the version in `deny.toml` in the `[[licenses.clarify]]` sections for `apollo-router-core`, `apollo-router` and `apollo-spaceport`.
-7. Run `cargo check` so the lock file gets updated.
-8. Run `cargo xtask check-compliance`.
-9. Push up a commit with the `*/Cargo.toml`, `Cargo.lock`, `CHANGELOG.md` and
+6. Run `cargo check` so the lock file gets updated.
+7. Run `cargo xtask check-compliance`.
+8. Push up a commit with the `*/Cargo.toml`, `Cargo.lock`, `CHANGELOG.md` and
     `NEXT_CHANGELOG.md` changes. The commit message should be "release: v#.#.#" or
     "release: v#.#.#-rc.#"
-10. Request review from the Router team.
+9. Request review from the Router team.
 
 ### Review
 

apollo-router-benchmarks/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "apollo-router-benchmarks"
-version = "0.1.0-preview.7"
+version = "0.9.0-rc.0"
 authors = ["Apollo Graph, Inc. <[email protected]>"]
 edition = "2021"
 license = "LicenseRef-ELv2"

apollo-router-core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "apollo-router-core"
-version = "0.1.0-preview.7"
+version = "0.9.0-rc.0"
 authors = ["Apollo Graph, Inc. <[email protected]>"]
 edition = "2021"
 license = "Elastic-2.0"

apollo-router/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "apollo-router"
-version = "0.1.0-preview.7"
+version = "0.9.0-rc.0"
 authors = ["Apollo Graph, Inc. <[email protected]>"]
 edition = "2021"
 license = "Elastic-2.0"

apollo-spaceport/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "apollo-spaceport"
-version = "0.1.0-preview.7"
+version = "0.9.0-rc.0"
 authors = ["Apollo Graph, Inc. <[email protected]>"]
 edition = "2021"
 license = "Elastic-2.0"

docs/source/containerization/docker.mdx

@@ -9,7 +9,7 @@ The default behaviour of the router images is suitable for a quickstart or devel
 
 Note: The [docker documentation](https://docs.docker.com/engine/reference/run/) for the run command may be helpful when reading through the examples.
 
-Note: The exact image version to use is your choice depending on which release you wish to use. In the following examples, replace `<image version>` with your chosen version. e.g.: `v0.1.0-preview.7`
+Note: The exact image version to use is your choice depending on which release you wish to use. In the following examples, replace `<image version>` with your chosen version. e.g.: `v0.9.0-rc.0`
 
 ## Override the configuration
 

docs/source/federation-version-support.mdx

@@ -23,6 +23,16 @@ against.
     </tr>
     </thead>
     <tbody>
+        <tr>
+        <td>v0.9.0-rc.0
+        </td>
+        <td>
+            2.0.2
+        </td>
+        <td>
+            2022-05-10
+        </td>
+    </tr>
     <tr>
         <td>v0.1.0-preview.7
         </td>

uplink/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "apollo-uplink"
-version = "0.1.0-preview.7"
+version = "0.9.0-rc.0"
 edition = "2021"
 build = "build.rs"
 

xtask/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "xtask"
-version = "0.1.0-preview.7"
+version = "0.9.0-rc.0"
 authors = ["Apollo Graph, Inc. <[email protected]>"]
 edition = "2021"
 license = "LicenseRef-ELv2"