-
Notifications
You must be signed in to change notification settings - Fork 272
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
release: v1.14.0 #2914
Merged
release: v1.14.0 #2914
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow sidecars, like coprocessors, in the official helm chart. <!-- start metadata --> **Checklist** Complete the checklist (and note appropriate exceptions) before a final PR is raised. - [x] Changes are compatible[^1] - [ ] Documentation[^2] completed - [x] Performance impact assessed and acceptable - Tests added and passing[^3] - [ ] Unit Tests - [ ] Integration Tests - [ ] Manual Tests **Exceptions** *Note any exceptions here* **Notes** [^1]. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. [^2]. Configuration is an important part of many changes. Where applicable please try to document configuration examples. [^3]. Tick whichever testing boxes are applicable. If you are adding Manual Tests: - please document the manual testing (extensively) in the Exceptions. - please raise a separate issue to automate the test and label it (or ask for it to be labeled) as `manual test` Co-authored-by: Gary Pennington <gary@apollographql.com>
Fix #2862, #2861, #2886 ### Coprocessor: add fields to the router and the subgraph stage This changeset adds several (read only) fields to coprocessor stages: router request: - path - method router response: - status_code subgraph response: - status_code It removes the`coprocessor.subgraph.all.response.uri` key (that was unused), with a migration. It also fixes a bug where a coprocessor operating at the `router_request` stage would fail to deserialize an empty body (which happens for GET requests). --------- Co-authored-by: Jesse Rosenberger <git@jro.cc> Co-authored-by: Gary Pennington <gary@apollographql.com>
This PR enables the `vendored-openssl` feature on the `git2` crate in the `xtask` workspace crate. Fixes #2904
Add the capability for Helm users to set extra labels attached to the router deployment and its pods. Co-authored-by: Gary Pennington <gary@apollographql.com>
This changeset updates thee xtask and router Cargo.lock.
uses cache-control headers from subgraphs to determine an overally cache-control policy partially addresses #326
Note: This PR should be marked as "Ready for review" only AFTER #2911 has merged into it. |
o0Ignition0o
reviewed
Apr 7, 2023
Thanks! Auto merge enabled. |
o0Ignition0o
approved these changes
Apr 7, 2023
bnjjj
approved these changes
Apr 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 particular PR should be true-merged to
main
.This PR represents the merge to
main
of the v1.14.0 release and follows up the release prep PR.This PR is mainly a merge commit, so reviewing every individual commit shown below is not necessary since those have been reviewed in their own PR.
However! Some things to review on this PR:
main
)If those things look good, this PR is good to merge.