Skip to content

0.81.0 #369

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
fylorn merged 1 commit into from
Oct 23, 2026
Merged

0.81.0 #369

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
42 changes: 21 additions & 21 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 Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ categories = ["network-programming", "web-programming::http-server"]

# 二进制走 CalVer，crate 走 SemVer —— 两者是两回事，卖给不同的人。
# 这里是 crate 的版本。
version = "0.80.0"
version = "0.81.0"

[workspace.dependencies]
# ── 内部 crate ───────────────────────────────────────────
Expand Down
14 changes: 14 additions & 0 deletions release-notes/0.81.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
This release keeps a conversation that carries encrypted history on the upstream that encrypted it, so moving a route to another upstream no longer breaks a Codex conversation that is under way.

**Upgrade notes**

- The control-plane protocol version stays at 51, and the request store's schema is unchanged; nothing is cleared.
- No configuration key is added, renamed or removed.

**Conversations with encrypted history stay on their upstream.** OpenAI Responses hands clients encrypted state to send back each turn (`encrypted_content`: reasoning, compacted history, and the messages Codex sub-agents report to each other), and only the account that encrypted it can read it. Before, a conversation moved to another upstream, for example after its route was changed, failed every turn with `invalid_encrypted_content`.

- The gateway now remembers which upstream last answered each conversation, across configuration reloads, a cold cache and quiet upstreams. A conversation that carried encrypted content is remembered for 30 days; the record does not survive a restart of core.
- When more than reasoning is encrypted, the conversation goes back to that upstream only, whatever its rule now picks, with no failover. If that upstream was removed, the request is refused with `gw.route.sealed_upstream_gone`.
- When only reasoning is encrypted, that upstream is tried first and the others remain as fallbacks.
- The route decision records this as the new reason `sealed`.
- An upstream that refuses encrypted content it cannot read (with a 400, or with an error inside the stream) now fails the request with `gw.upstream.sealed_elsewhere`, which names the upstream and explains that the history was encrypted by another one.
Loading