Skip to content

Sync main → develop (PR #317) #341

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Sep 10, 2025
Merged

Sync main → develop (PR #317) #341

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2914318
docs: improve wording in limitations docs
DaleSeo Sep 9, 2025
cc95f86
Merge pull request #339 from apollographql/imporove-wording
mabuyo Sep 9, 2025
d11d81a
fix(deps): update rust crate tracing-subscriber to v0.3.20 [security]…
svc-secops Sep 9, 2025
fa306e3
Merge remote-tracking branch 'origin/main' into sync/main-into-develo…
apollo-bot2 Sep 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 15 additions & 37 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion docs/source/limitations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,4 +39,4 @@

#### Future plans

We plan to address this limitation in a future release by implementing proper token exchange or separate authentication flows for upstream APIs, while still supporting the enterprise requirement for user identity propagation.
We plan to address this limitation in a future release by implementing token exchange or separate authentication flows for upstream APIs, while still supporting the enterprise requirement for user identity propagation.

Check warning on line 42 in docs/source/limitations.mdx

View check run for this annotation

Apollo Librarian / AI Style Review

docs/source/limitations.mdx#L42 

Use "Apollo" instead of "we" for clarity. The word "adding" is preferred over "implementing" for simplicity.

```suggestion
Apollo plans to address this limitation in a future release by adding token exchange or separate authentication flows for upstream APIs, while still supporting the enterprise requirement for user identity propagation.
```