From 158e5d95936273ade1860824490ced85f3e150c7 Mon Sep 17 00:00:00 2001 From: Jesse Rosenberger Date: Tue, 22 Oct 2024 15:40:36 +0300 Subject: [PATCH] prep release: v1.57.0 --- .../feat_bnjjj_feat_schema_id_context.md | 23 --- .changesets/feat_rhai_uri_port.md | 20 --- .../feat_simon_replatform_introspection.md | 12 -- .../fix_feature_rhairouterrequesturi.md | 20 --- .changesets/fix_fix_typename.md | 23 --- .changesets/fix_renee_router_815_changeset.md | 11 -- .../fix_router_bridge_v0_6_4_v2_9_3.md | 10 -- CHANGELOG.md | 135 ++++++++++++++++++ Cargo.lock | 8 +- apollo-federation/Cargo.toml | 2 +- apollo-router-benchmarks/Cargo.toml | 2 +- apollo-router-scaffold/Cargo.toml | 2 +- .../templates/base/Cargo.template.toml | 2 +- .../templates/base/xtask/Cargo.template.toml | 2 +- apollo-router/Cargo.toml | 4 +- .../tracing/docker-compose.datadog.yml | 2 +- dockerfiles/tracing/docker-compose.jaeger.yml | 2 +- dockerfiles/tracing/docker-compose.zipkin.yml | 2 +- docs/source/federation-version-support.mdx | 10 +- helm/chart/router/Chart.yaml | 4 +- helm/chart/router/README.md | 6 +- licenses.html | 73 +++++++++- scripts/install.sh | 2 +- 23 files changed, 231 insertions(+), 146 deletions(-) delete mode 100644 .changesets/feat_bnjjj_feat_schema_id_context.md delete mode 100644 .changesets/feat_rhai_uri_port.md delete mode 100644 .changesets/feat_simon_replatform_introspection.md delete mode 100644 .changesets/fix_feature_rhairouterrequesturi.md delete mode 100644 .changesets/fix_fix_typename.md delete mode 100644 .changesets/fix_renee_router_815_changeset.md delete mode 100644 .changesets/fix_router_bridge_v0_6_4_v2_9_3.md diff --git a/.changesets/feat_bnjjj_feat_schema_id_context.md b/.changesets/feat_bnjjj_feat_schema_id_context.md deleted file mode 100644 index bb94e47c99..0000000000 --- a/.changesets/feat_bnjjj_feat_schema_id_context.md +++ /dev/null @@ -1,23 +0,0 @@ -### Support new `request_context` selector for telemetry ([PR #6160](https://github.com/apollographql/router/pull/6160)) - -The router supports a new `request_context` selector for telemetry that enables access to the supergraph schema ID. - -You can configure the context to access the supergraph schema ID at the router service level: - -```yaml -telemetry: - instrumentation: - events: - router: - my.request_event: - message: "my request event message" - level: info - on: request - attributes: - schema.id: - request_context: "apollo::supergraph_schema_id" # The key containing the supergraph schema id -``` - -You can use the selector in any service at any stage. While this example applies to `events` attributes, the selector can also be used on spans and instruments. - -By [@bnjjj](https://github.com/bnjjj) in https://github.com/apollographql/router/pull/6160 \ No newline at end of file diff --git a/.changesets/feat_rhai_uri_port.md b/.changesets/feat_rhai_uri_port.md deleted file mode 100644 index 22688564b3..0000000000 --- a/.changesets/feat_rhai_uri_port.md +++ /dev/null @@ -1,20 +0,0 @@ -### Support reading and setting `port` on request URIs using Rhai ([Issue #5437](https://github.com/apollographql/router/issues/5437)) - -Custom Rhai scripts in the router now support the `request.uri.port` and `request.subgraph.uri.port` functions for reading and setting URI ports. These functions enable you to update the full URI for subgraph fetches. For example: - -```rust -fn subgraph_service(service, subgraph){ - service.map_request(|request|{ - log_info(`${request.subgraph.uri.port}`); - if request.subgraph.uri.port == {} { - log_info("Port is not explicitly set"); - } - request.subgraph.uri.host = "api.apollographql.com"; - request.subgraph.uri.path = "/api/graphql"; - request.subgraph.uri.port = 1234; - log_info(`${request.subgraph.uri}`); - }); -} -``` - -By [@lleadbet](https://github.com/lleadbet) in https://github.com/apollographql/router/pull/5439 diff --git a/.changesets/feat_simon_replatform_introspection.md b/.changesets/feat_simon_replatform_introspection.md deleted file mode 100644 index 06c6788f28..0000000000 --- a/.changesets/feat_simon_replatform_introspection.md +++ /dev/null @@ -1,12 +0,0 @@ -### Remove legacy schema introspection ([PR #6139](https://github.com/apollographql/router/pull/6139)) - -Schema introspection in the router now runs natively without JavaScript. We have high confidence that the new native implementation returns responses that match the previous Javascript implementation, based on differential testing: fuzzing arbitrary queries against a large schema, and testing a corpus of customer schemas against a comprehensive query. - -Changes to the router's YAML configuration: - -* The `experimental_introspection_mode` key has been removed, with the `new` mode as the only behavior in this release. -* The `supergraph.query_planning.legacy_introspection_caching` key is removed, with the behavior in this release now similar to what was `false`: introspection responses are not part of the query plan cache but instead in a separate, small in-memory—only cache. - -When using the above deprecated configuration options, the router's automatic configuration migration will ensure that existing configuration continue to work until the next major version of the router. To simplify major upgrades, we recommend reviewing incremental updates to your YAML configuration by comparing the output of `./router config upgrade --config path/to/config.yaml` with your existing configuration. - -By [@SimonSapin](https://github.com/SimonSapin) in https://github.com/apollographql/router/pull/6139 diff --git a/.changesets/fix_feature_rhairouterrequesturi.md b/.changesets/fix_feature_rhairouterrequesturi.md deleted file mode 100644 index 9706a0a11f..0000000000 --- a/.changesets/fix_feature_rhairouterrequesturi.md +++ /dev/null @@ -1,20 +0,0 @@ -### Support URI and method properties for router request in Rhai ([PR #6147](https://github.com/apollographql/router/pull/6147)) - -The router now supports accessing `request.uri` and `request.method` properties from custom Rhai scripts. - -Previously, when trying to access `request.uri` and `request.method` on a router request in Rhai, the router would return error messages stating the properties were undefined. - -An example Rhai script using these properties: - -```rhai -fn router_service(service) { - let router_request_callback = Fn("router_request_callback"); - service.map_request(router_request_callback); -} - -fn router_request_callback (request) { - log_info(`Router Request... Host: ${request.uri.host}, Path: ${request.uri.path}`); -} -``` - -By [@andrewmcgivery](https://github.com/andrewmcgivery) in https://github.com/apollographql/router/pull/6114 diff --git a/.changesets/fix_fix_typename.md b/.changesets/fix_fix_typename.md deleted file mode 100644 index 6a80079130..0000000000 --- a/.changesets/fix_fix_typename.md +++ /dev/null @@ -1,23 +0,0 @@ -### Fix various edge cases for `__typename` field ([PR #6009](https://github.com/apollographql/router/pull/6009)) - -The router now correctly handles the `__typename` field used on operation root types, even when the subgraph's root type has a name that differs from the supergraph's root type. - -For example, given a query like this: - -```graphql -{ - ...RootFragment -} - -fragment RootFragment on Query { - __typename - me { - name - } -} -``` -Even if the subgraph's root type returns a `__typename` that differs from `Query`, the router will still use `Query` as the value of the `__typename` field. - -This change also includes fixes for other edge cases related to the handling of `__typename` fields. For a detailed technical description of the edge cases that were fixed, please see [this description](https://github.com/apollographql/router/pull/6009#issue-2529717207). - -By [@IvanGoncharov](https://github.com/IvanGoncharov) in https://github.com/apollographql/router/pull/6009 \ No newline at end of file diff --git a/.changesets/fix_renee_router_815_changeset.md b/.changesets/fix_renee_router_815_changeset.md deleted file mode 100644 index 2adf7616d1..0000000000 --- a/.changesets/fix_renee_router_815_changeset.md +++ /dev/null @@ -1,11 +0,0 @@ -### Fix cost calculation for subgraph requests with named fragments ([PR #6162](https://github.com/apollographql/router/issues/6162)) - -In some cases where subgraph GraphQL operations contain named fragments and abstract types, demand control used the wrong type for cost calculation, and could reject valid operations. -Now, the correct type is used. - -This fixes errors of the form: -``` -Attempted to look up a field on type MyInterface, but the field does not exist -``` - -By [@goto-bus-stop](https://github.com/goto-bus-stop) in https://github.com/apollographql/router/pull/6162 \ No newline at end of file diff --git a/.changesets/fix_router_bridge_v0_6_4_v2_9_3.md b/.changesets/fix_router_bridge_v0_6_4_v2_9_3.md deleted file mode 100644 index 2d0325dc1f..0000000000 --- a/.changesets/fix_router_bridge_v0_6_4_v2_9_3.md +++ /dev/null @@ -1,10 +0,0 @@ -### Update router-bridge@0.6.4+v2.9.3 ([PR #6161](https://github.com/apollographql/router/pull/6161)) - -Updates to latest router-bridge and federation version. This federation version: -- Fixes a query planning bug where operation variables for a subgraph query wouldn't match what's used in that query. -- Fixes a query planning bug where directives applied to `__typename` may be omitted in the subgraph query. -- Fixes a query planning inefficiency where some redundant subgraph queries were not removed. -- Fixes a query planning inefficiency where some redundant inline fragments in `@key`/`@requires` selection sets were not optimized away. -- Fixes a query planning inefficiency where unnecessary subgraph jumps were being added when using `@context`/`@fromContext`. - -By [@sachindshinde](https://github.com/sachindshinde) in https://github.com/apollographql/router/pull/6161 \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md index be7d77c929..adc42690e4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,141 @@ All notable changes to Router will be documented in this file. This project adheres to [Semantic Versioning v2.0.0](https://semver.org/spec/v2.0.0.html). +# [1.57.0] - 2024-10-22 + +> [!IMPORTANT] +> If you have enabled [Distributed query plan caching](https://www.apollographql.com/docs/router/configuration/distributed-caching/#distributed-query-plan-caching), updates to the query planner in this release will result in query plan caches being re-generated rather than re-used. On account of this, you should anticipate additional cache regeneration cost when updating between these versions while the new query plans come into service. + +## 🚀 Features + +### Remove legacy schema introspection ([PR #6139](https://github.com/apollographql/router/pull/6139)) + +Schema introspection in the router now runs natively without JavaScript. We have high confidence that the new native implementation returns responses that match the previous Javascript implementation, based on differential testing: fuzzing arbitrary queries against a large schema, and testing a corpus of customer schemas against a comprehensive query. + +Changes to the router's YAML configuration: + +* The `experimental_introspection_mode` key has been removed, with the `new` mode as the only behavior in this release. +* The `supergraph.query_planning.legacy_introspection_caching` key is removed, with the behavior in this release now similar to what was `false`: introspection responses are not part of the query plan cache but instead in a separate, small in-memory—only cache. + +When using the above deprecated configuration options, the router's automatic configuration migration will ensure that existing configuration continue to work until the next major version of the router. To simplify major upgrades, we recommend reviewing incremental updates to your YAML configuration by comparing the output of `./router config upgrade --config path/to/config.yaml` with your existing configuration. + +By [@SimonSapin](https://github.com/SimonSapin) in https://github.com/apollographql/router/pull/6139 + +### Support new `request_context` selector for telemetry ([PR #6160](https://github.com/apollographql/router/pull/6160)) + +The router supports a new `request_context` selector for telemetry that enables access to the supergraph schema ID. + +You can configure the context to access the supergraph schema ID at the router service level: + +```yaml +telemetry: + instrumentation: + events: + router: + my.request_event: + message: "my request event message" + level: info + on: request + attributes: + schema.id: + request_context: "apollo::supergraph_schema_id" # The key containing the supergraph schema id +``` + +You can use the selector in any service at any stage. While this example applies to `events` attributes, the selector can also be used on spans and instruments. + +By [@bnjjj](https://github.com/bnjjj) in https://github.com/apollographql/router/pull/6160 + +### Support reading and setting `port` on request URIs using Rhai ([Issue #5437](https://github.com/apollographql/router/issues/5437)) + +Custom Rhai scripts in the router now support the `request.uri.port` and `request.subgraph.uri.port` functions for reading and setting URI ports. These functions enable you to update the full URI for subgraph fetches. For example: + +```rust +fn subgraph_service(service, subgraph){ + service.map_request(|request|{ + log_info(``); + if request.subgraph.uri.port == {} { + log_info("Port is not explicitly set"); + } + request.subgraph.uri.host = "api.apollographql.com"; + request.subgraph.uri.path = "/api/graphql"; + request.subgraph.uri.port = 1234; + log_info(``); + }); +} +``` + +By [@lleadbet](https://github.com/lleadbet) in https://github.com/apollographql/router/pull/5439 + +## 🐛 Fixes + +### Fix various edge cases for `__typename` field ([PR #6009](https://github.com/apollographql/router/pull/6009)) + +The router now correctly handles the `__typename` field used on operation root types, even when the subgraph's root type has a name that differs from the supergraph's root type. + +For example, given a query like this: + +```graphql +{ + ...RootFragment +} + +fragment RootFragment on Query { + __typename + me { + name + } +} +``` + +Even if the subgraph's root type returns a `__typename` that differs from `Query`, the router will still use `Query` as the value of the `__typename` field. + +This change also includes fixes for other edge cases related to the handling of `__typename` fields. For a detailed technical description of the edge cases that were fixed, please see [this description](https://github.com/apollographql/router/pull/6009#issue-2529717207). + +By [@IvanGoncharov](https://github.com/IvanGoncharov) in https://github.com/apollographql/router/pull/6009 + +### Support `uri` and `method` properties on router "request" objects in Rhai ([PR #6147](https://github.com/apollographql/router/pull/6147)) + +The router now supports accessing `request.uri` and `request.method` properties from custom Rhai scripts. Previously, when trying to access `request.uri` and `request.method` on a router request in Rhai, the router would return error messages stating the properties were undefined. + +An example Rhai script using these properties: + +```rhai +fn router_service(service) { + let router_request_callback = Fn("router_request_callback"); + service.map_request(router_request_callback); +} + +fn router_request_callback (request) { + log_info(`Router Request... Host: , Path: `); +} +``` + +By [@andrewmcgivery](https://github.com/andrewmcgivery) in https://github.com/apollographql/router/pull/6114 + +### Cost calculation for subgraph requests with named fragments ([PR #6162](https://github.com/apollographql/router/issues/6162)) + +In some cases where subgraph GraphQL operations contain named fragments and abstract types, demand control used the wrong type for cost calculation, and could reject valid operations. Now, the correct type is used. + +This fixes errors of the form: + +``` +Attempted to look up a field on type MyInterface, but the field does not exist +``` + +By [@goto-bus-stop](https://github.com/goto-bus-stop) in https://github.com/apollographql/router/pull/6162 + +### Federation v2.9.3 ([PR #6161](https://github.com/apollographql/router/pull/6161)) + +This release updates to Federation v2.9.3, with query planner fixes: + +- Fixes a query planning bug where operation variables for a subgraph query wouldn't match what's used in that query. +- Fixes a query planning bug where directives applied to `__typename` may be omitted in the subgraph query. +- Fixes a query planning inefficiency where some redundant subgraph queries were not removed. +- Fixes a query planning inefficiency where some redundant inline fragments in `@key`/`@requires` selection sets were not optimized away. +- Fixes a query planning inefficiency where unnecessary subgraph jumps were being added when using `@context`/`@fromContext`. + +By [@sachindshinde](https://github.com/sachindshinde) in https://github.com/apollographql/router/pull/6161 + # [1.56.0] - 2024-10-01 > [!IMPORTANT] diff --git a/Cargo.lock b/Cargo.lock index 1d54cc9ab7..58595d4317 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -178,7 +178,7 @@ dependencies = [ [[package]] name = "apollo-federation" -version = "1.57.0-rc.0" +version = "1.57.0" dependencies = [ "apollo-compiler", "derive_more", @@ -229,7 +229,7 @@ dependencies = [ [[package]] name = "apollo-router" -version = "1.57.0-rc.0" +version = "1.57.0" dependencies = [ "access-json", "ahash", @@ -397,7 +397,7 @@ dependencies = [ [[package]] name = "apollo-router-benchmarks" -version = "1.57.0-rc.0" +version = "1.57.0" dependencies = [ "apollo-parser", "apollo-router", @@ -413,7 +413,7 @@ dependencies = [ [[package]] name = "apollo-router-scaffold" -version = "1.57.0-rc.0" +version = "1.57.0" dependencies = [ "anyhow", "cargo-scaffold", diff --git a/apollo-federation/Cargo.toml b/apollo-federation/Cargo.toml index c9a56b0a03..56def7c08c 100644 --- a/apollo-federation/Cargo.toml +++ b/apollo-federation/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "apollo-federation" -version = "1.57.0-rc.0" +version = "1.57.0" authors = ["The Apollo GraphQL Contributors"] edition = "2021" description = "Apollo Federation" diff --git a/apollo-router-benchmarks/Cargo.toml b/apollo-router-benchmarks/Cargo.toml index dc9913f8f7..ad2cd569c7 100644 --- a/apollo-router-benchmarks/Cargo.toml +++ b/apollo-router-benchmarks/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "apollo-router-benchmarks" -version = "1.57.0-rc.0" +version = "1.57.0" authors = ["Apollo Graph, Inc. "] edition = "2021" license = "Elastic-2.0" diff --git a/apollo-router-scaffold/Cargo.toml b/apollo-router-scaffold/Cargo.toml index 8e75e05e2e..a598f6f5ee 100644 --- a/apollo-router-scaffold/Cargo.toml +++ b/apollo-router-scaffold/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "apollo-router-scaffold" -version = "1.57.0-rc.0" +version = "1.57.0" authors = ["Apollo Graph, Inc. "] edition = "2021" license = "Elastic-2.0" diff --git a/apollo-router-scaffold/templates/base/Cargo.template.toml b/apollo-router-scaffold/templates/base/Cargo.template.toml index e5ded8b6dc..3855918e82 100644 --- a/apollo-router-scaffold/templates/base/Cargo.template.toml +++ b/apollo-router-scaffold/templates/base/Cargo.template.toml @@ -22,7 +22,7 @@ apollo-router = { path ="{{integration_test}}apollo-router" } apollo-router = { git="https://github.com/apollographql/router.git", branch="{{branch}}" } {{else}} # Note if you update these dependencies then also update xtask/Cargo.toml -apollo-router = "1.57.0-rc.0" +apollo-router = "1.57.0" {{/if}} {{/if}} async-trait = "0.1.52" diff --git a/apollo-router-scaffold/templates/base/xtask/Cargo.template.toml b/apollo-router-scaffold/templates/base/xtask/Cargo.template.toml index c7275ff8b8..0c164855ff 100644 --- a/apollo-router-scaffold/templates/base/xtask/Cargo.template.toml +++ b/apollo-router-scaffold/templates/base/xtask/Cargo.template.toml @@ -13,7 +13,7 @@ apollo-router-scaffold = { path ="{{integration_test}}apollo-router-scaffold" } {{#if branch}} apollo-router-scaffold = { git="https://github.com/apollographql/router.git", branch="{{branch}}" } {{else}} -apollo-router-scaffold = { git = "https://github.com/apollographql/router.git", tag = "v1.57.0-rc.0" } +apollo-router-scaffold = { git = "https://github.com/apollographql/router.git", tag = "v1.57.0" } {{/if}} {{/if}} anyhow = "1.0.58" diff --git a/apollo-router/Cargo.toml b/apollo-router/Cargo.toml index ccb81659bf..020e624ef9 100644 --- a/apollo-router/Cargo.toml +++ b/apollo-router/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "apollo-router" -version = "1.57.0-rc.0" +version = "1.57.0" authors = ["Apollo Graph, Inc. "] repository = "https://github.com/apollographql/router/" documentation = "https://docs.rs/apollo-router" @@ -62,7 +62,7 @@ features = ["docs_rs"] access-json = "0.1.0" anyhow = "1.0.86" apollo-compiler.workspace = true -apollo-federation = { path = "../apollo-federation", version = "=1.57.0-rc.0" } +apollo-federation = { path = "../apollo-federation", version = "=1.57.0" } arc-swap = "1.6.0" async-channel = "1.9.0" async-compression = { version = "0.4.6", features = [ diff --git a/dockerfiles/tracing/docker-compose.datadog.yml b/dockerfiles/tracing/docker-compose.datadog.yml index 804bbbe0af..c6b46fcd7e 100644 --- a/dockerfiles/tracing/docker-compose.datadog.yml +++ b/dockerfiles/tracing/docker-compose.datadog.yml @@ -3,7 +3,7 @@ services: apollo-router: container_name: apollo-router - image: ghcr.io/apollographql/router:v1.57.0-rc.0 + image: ghcr.io/apollographql/router:v1.57.0 volumes: - ./supergraph.graphql:/etc/config/supergraph.graphql - ./router/datadog.router.yaml:/etc/config/configuration.yaml diff --git a/dockerfiles/tracing/docker-compose.jaeger.yml b/dockerfiles/tracing/docker-compose.jaeger.yml index 4e0f42eb3e..71d4e88301 100644 --- a/dockerfiles/tracing/docker-compose.jaeger.yml +++ b/dockerfiles/tracing/docker-compose.jaeger.yml @@ -4,7 +4,7 @@ services: apollo-router: container_name: apollo-router #build: ./router - image: ghcr.io/apollographql/router:v1.57.0-rc.0 + image: ghcr.io/apollographql/router:v1.57.0 volumes: - ./supergraph.graphql:/etc/config/supergraph.graphql - ./router/jaeger.router.yaml:/etc/config/configuration.yaml diff --git a/dockerfiles/tracing/docker-compose.zipkin.yml b/dockerfiles/tracing/docker-compose.zipkin.yml index 4e2cdf94f7..2e6eea86ba 100644 --- a/dockerfiles/tracing/docker-compose.zipkin.yml +++ b/dockerfiles/tracing/docker-compose.zipkin.yml @@ -4,7 +4,7 @@ services: apollo-router: container_name: apollo-router build: ./router - image: ghcr.io/apollographql/router:v1.57.0-rc.0 + image: ghcr.io/apollographql/router:v1.57.0 volumes: - ./supergraph.graphql:/etc/config/supergraph.graphql - ./router/zipkin.router.yaml:/etc/config/configuration.yaml diff --git a/docs/source/federation-version-support.mdx b/docs/source/federation-version-support.mdx index defc58f1c4..e7d7a4aa98 100644 --- a/docs/source/federation-version-support.mdx +++ b/docs/source/federation-version-support.mdx @@ -37,7 +37,15 @@ The table below shows which version of federation each router release is compile - v1.56.0 and later (see latest releases) + v1.57.0 and later (see latest releases) + + + 2.9.3 + + + + + v1.56.0 2.9.2 diff --git a/helm/chart/router/Chart.yaml b/helm/chart/router/Chart.yaml index f5510fbc62..adfef3761f 100644 --- a/helm/chart/router/Chart.yaml +++ b/helm/chart/router/Chart.yaml @@ -20,10 +20,10 @@ type: application # so it matches the shape of our release process and release automation. # By proxy of that decision, this version uses SemVer 2.0.0, though the prefix # of "v" is not included. -version: 1.57.0-rc.0 +version: 1.57.0 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. # It is recommended to use it with quotes. -appVersion: "v1.57.0-rc.0" +appVersion: "v1.57.0" diff --git a/helm/chart/router/README.md b/helm/chart/router/README.md index 5605bb12dd..44c483d39b 100644 --- a/helm/chart/router/README.md +++ b/helm/chart/router/README.md @@ -2,7 +2,7 @@ [router](https://github.com/apollographql/router) Rust Graph Routing runtime for Apollo Federation -![Version: 1.57.0-rc.0](https://img.shields.io/badge/Version-1.57.0--rc.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v1.57.0-rc.0](https://img.shields.io/badge/AppVersion-v1.57.0--rc.0-informational?style=flat-square) +![Version: 1.57.0](https://img.shields.io/badge/Version-1.57.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v1.57.0](https://img.shields.io/badge/AppVersion-v1.57.0-informational?style=flat-square) ## Prerequisites @@ -11,7 +11,7 @@ ## Get Repo Info ```console -helm pull oci://ghcr.io/apollographql/helm-charts/router --version 1.57.0-rc.0 +helm pull oci://ghcr.io/apollographql/helm-charts/router --version 1.57.0 ``` ## Install Chart @@ -19,7 +19,7 @@ helm pull oci://ghcr.io/apollographql/helm-charts/router --version 1.57.0-rc.0 **Important:** only helm3 is supported ```console -helm upgrade --install [RELEASE_NAME] oci://ghcr.io/apollographql/helm-charts/router --version 1.57.0-rc.0 --values my-values.yaml +helm upgrade --install [RELEASE_NAME] oci://ghcr.io/apollographql/helm-charts/router --version 1.57.0 --values my-values.yaml ``` _See [configuration](#configuration) below._ diff --git a/licenses.html b/licenses.html index 5b44697f9d..01b9b1d8ef 100644 --- a/licenses.html +++ b/licenses.html @@ -44,8 +44,8 @@

Third Party Licenses

Overview of licenses:

This project is dual-licensed under the Unlicense and MIT licenses.
 
@@ -15606,7 +15639,6 @@ 

Used by:

Mozilla Public License 2.0

Used by:

Mozilla Public License Version 2.0
@@ -15989,8 +16021,8 @@ 

Used by:

Mozilla Public License 2.0

Used by:

Mozilla Public License Version 2.0
 ==================================
@@ -16365,6 +16397,35 @@ 

Used by:

This Source Code Form is "Incompatible With Secondary Licenses", as defined by the Mozilla Public License, v. 2.0. +
+ +
  • +

    Mozilla Public License 2.0

    +

    Used by:

    + +
    This packge contains a modified version of ca-bundle.crt:
    +
    +ca-bundle.crt -- Bundle of CA Root Certificates
    +
    +Certificate data from Mozilla as of: Thu Nov  3 19:04:19 2011#
    +This is a bundle of X.509 certificates of public Certificate Authorities
    +(CA). These were automatically extracted from Mozilla's root certificates
    +file (certdata.txt).  This file can be found in the mozilla source tree:
    +http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt?raw=1#
    +It contains the certificates in PEM format and therefore
    +can be directly used with curl / libcurl / php_curl, or with
    +an Apache+mod_ssl webserver for SSL client authentication.
    +Just configure this file as the SSLCACertificateFile.#
    +
    +***** BEGIN LICENSE BLOCK *****
    +This Source Code Form is subject to the terms of the Mozilla Public License,
    +v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain
    +one at http://mozilla.org/MPL/2.0/.
    +
    +***** END LICENSE BLOCK *****
    +@(#) $RCSfile: certdata.txt,v $ $Revision: 1.80 $ $Date: 2011/11/03 15:11:58 $
     
  • diff --git a/scripts/install.sh b/scripts/install.sh index ace0ebc840..1123fb1802 100755 --- a/scripts/install.sh +++ b/scripts/install.sh @@ -11,7 +11,7 @@ BINARY_DOWNLOAD_PREFIX="https://github.com/apollographql/router/releases/downloa # Router version defined in apollo-router's Cargo.toml # Note: Change this line manually during the release steps. -PACKAGE_VERSION="v1.57.0-rc.0" +PACKAGE_VERSION="v1.57.0" download_binary() { downloader --check