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

release: v1.14.0 #2914

Merged
merged 9 commits into from
Apr 7, 2023
Merged

release: v1.14.0 #2914

merged 9 commits into from
Apr 7, 2023

Conversation

abernix
Copy link
Member

@abernix abernix commented Apr 6, 2023

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:

  • Does this PR target the right branch? (usually, main)
  • Are the appropriate version bumps and release note edits in the end of the commit list (or within the last few commits). In other words, did the release prep PR actually land on this branch?

If those things look good, this PR is good to merge.

abernix and others added 7 commits April 4, 2023 10:40
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
@abernix
Copy link
Member Author

abernix commented Apr 6, 2023

Note: This PR should be marked as "Ready for review" only AFTER #2911 has merged into it.

@bnjjj bnjjj marked this pull request as ready for review April 7, 2023 08:08
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
@abernix abernix enabled auto-merge April 7, 2023 08:13
@abernix
Copy link
Member Author

abernix commented Apr 7, 2023

Thanks! Auto merge enabled.

@abernix abernix merged commit 63d7145 into main Apr 7, 2023
@abernix abernix deleted the 1.14.0 branch April 7, 2023 08:31
o0Ignition0o added a commit that referenced this pull request Apr 7, 2023
@abernix abernix added the release label Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants