Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency apollographql/router to v1.33.0 #1767

Merged
merged 1 commit into from
Oct 20, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 17, 2023

Mend Renovate

This PR contains the following updates:

Package Update Change
apollographql/router minor v1.32.0 -> v1.33.0

Release Notes

apollographql/router (apollographql/router)

v1.33.0

Compare Source

🚀 Features

Add hasNext to SupergraphRequest (Issue #​4016)

Coprocessors multi-part response support has been enhanced to include hasNext, allowing you to determine when a request has completed.

When stage is SupergraphResponse, hasNext if present and true indicates that there will be subsequent SupergraphResponse calls to the co-processor for each multi-part (@defer/subscriptions) response.

See the coprocessor documentation for more details.

By @​BrynCooke in https://github.com/apollographql/router/pull/4017

Expose the ability to set topology spread constraints on the helm chart (3891)

Give developers the ability to set topology spread constraints that can be used to guarantee that federation pods are spread out evenly across AZs.

By @​bjoernw in https://github.com/apollographql/router/pull/3892

🐛 Fixes

Ignore JWKS keys which aren't supported by the router (Issue #​3853)

If you have a JWKS which contains a key which has an algorithm (alg) which the router doesn't recognise, then the entire JWKS is disregarded even if there were other keys in the JWKS which the router could use.

We have changed the JWKS processing logic so that we remove entries with an unrecognised algorithm from the list of available keys. We print a warning with the name of the algorithm for each removed entry.

By @​garypen in https://github.com/apollographql/router/pull/3922

Fix panic when streaming responses to co-processor (Issue #​4013)

Streamed responses will no longer cause a panic in the co-processor plugin. This affected defer and stream queries.

By @​BrynCooke in https://github.com/apollographql/router/pull/4014

Only reject defer/subscriptions if actually part of a batch (Issue #​3956)

Fix the checking logic so that deferred queries or subscriptions will only be rejected when experimental batching is enabled and the operations are part of a batch.

Without this fix, all subscriptions or deferred queries would be rejected when experimental batching support was enabled.

By @​garypen in https://github.com/apollographql/router/pull/3959

Fix requires selection in arrays (Issue #​3972)

When a field has a @requires annotation that selects an array, and some fields are missing in that array or some of the elements are null, the router would short circuit the selection and remove the entire array. This relaxes the condition to allow nulls in the selected array

By @​Geal in https://github.com/apollographql/router/pull/3975

Fix router hang when opening the explorer, prometheus or health check page (Issue #​3941)

The Router did not gracefully shutdown when an idle connections are made by a client, and would instead hang. In particular, web browsers make such connection in anticipation of future traffic.

This is now fixed, and the Router will now gracefully shut down in a timely fashion.

By @​Geal in https://github.com/apollographql/router/pull/3969

Fix hang and high CPU usage when compressing small responses (PR #​3961)

When returning small responses (less than 10 bytes) and compressing them using gzip, the router could go into an infinite loop

By @​Geal in https://github.com/apollographql/router/pull/3961

📃 Configuration

Add enabled field for telemetry exporters (PR #​3952)

Telemetry configuration now supports enabled on all exporters. This allows exporters to be disabled without removing them from the configuration and in addition allows for a more streamlined default configuration.

telemetry:
  tracing: 
    datadog:
+      enabled: true
    jaeger:
+      enabled: true
    otlp:
+      enabled: true
    zipkin:
+      enabled: true

Existing configurations will be migrated to the new format automatically on startup. However, you should update your configuration to use the new format as soon as possible.

By @​BrynCooke in https://github.com/apollographql/router/pull/3952

🛠 Maintenance

Create a replacement self-signed server certificate: 10 years lifespan (Issue #​3998)

This certificate is only used for testing, so 10 years lifespan is acceptable.

By @​garypen in https://github.com/apollographql/router/pull/4009

📚 Documentation

Updated documentation for deploying router (PR #​3943)

Updated documentation for containerized router deployments, with guides and examples for deploying on Kubernetes and running on Docker.

By @​shorgi in https://github.com/apollographql/router/pull/3943

Document guidance for request and response buffering (Issue #​3838)

Provides specific guidance on request and response buffering within the router.

By @​garypen in https://github.com/apollographql/router/pull/3970


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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/apollographql-router-1.x branch from 48a6968 to cdbe1af Compare October 20, 2023 14:38
@EverlastingBugstopper EverlastingBugstopper merged commit b9da8c5 into main Oct 20, 2023
7 of 8 checks passed
@EverlastingBugstopper EverlastingBugstopper deleted the renovate/apollographql-router-1.x branch October 20, 2023 14:47
@EverlastingBugstopper EverlastingBugstopper added this to the vNext milestone Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant