chore(deps): update ghcr.io/apollographql/router docker tag to v1.36.0 #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.35.0
->v1.36.0
Release Notes
apollographql/router (ghcr.io/apollographql/router)
v1.36.0
Compare Source
🚀 Features
Run new (non-load-bearing) Rust validation out-of-band to help identify deltas (Issue#4159)
As part of the process to replace JavaScript validation with a more performant Rust validation in the router, we are enabling the router to run both validations as a default. This allows us to definitively assess reliability and stability of Rust validation before completely removing JavaScript validation. As before, it's possible to toggle between implementations using the
experimental_graphql_validation_mode
config key. Possible values are:new
(runs only Rust-based validation),legacy
(runs only JS-based validation),both
(runs both in comparison, logging errors if a difference arises).The
both
mode is now the default, which will result in no client-facing impact but will output errors to the Router's logs if a discrepancy is recorded. If you discover discrepancies in your logs, please open an issue.By @lrlna in https://github.com/apollographql/router/pull/4161
🐛 Fixes
Fix fragment usage with
@interfaceObject
(Issue #3855)When requesting
__typename
under a fragment under an interface, from a subgraph adding fields to that interface with the@interfaceObject
directive, the router was returning the interface name instead of the concrete type name. This is now fixed at the query planner level.By @geal in https://github.com/apollographql/router/pull/4363
TLS client configuration override for Redis (Issue #3551)
It is now possible to set up a client certificate or override the root certificate authority list for Redis connections, through the
tls
section under Redis configuration. Options follow the same format as subgraph TLS configuration:By @Geal in https://github.com/apollographql/router/pull/4304
span_mode: spec_compliant
not applied correctly (Issue #4335)Previously,
telemetry.instrumentation.spans.span_mode.spec_compliant
was not being correctly applied. This resulted in extra request spans that should not have been present in spec compliant mode, whererouter.supergraph.subgraph
was incorrectly output asrequest.router.supergraph.subgraph
. This has been fixed in this release.By @BrynCooke in https://github.com/apollographql/router/pull/4341
🛠 Maintenance
chore: Update zerocopy dependency (PR #4403)
This changeset updates zerocopy to 0.7.31, which has a fix for https://rustsec.org/advisories/RUSTSEC-2023-0074.
By @o0Ignition0o in https://github.com/apollographql/router/pull/4403
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.