Repository navigation
backport: preserve server compatibility on 2.91.3 - #14
Merged
jack-o-mania merged 10 commits intoOct 31, 2026
Merged
Conversation
Keep stored ChatGPT pool accounts visible and refreshable when the native Codex home is proven absent. Preserve native identity and reauthentication state without creating a home or relaxing credential-mutation claims. Validate OpenCodex storage before the missing-home fallback, and surface invalid home-resolution failures. Add isolated regressions for list/refresh routes and synchronize account-list guidance across all published locales. (cherry picked from commit 4abfcc6) (cherry picked from commit ea3e96f)
(cherry picked from commit 467d381)
(cherry picked from commit b0bcc06)
(cherry picked from commit e464250)
(cherry picked from commit 733583f8d4cf687eef5c0059c2010e106e5482f3) (cherry picked from commit c0263ad)
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
✅ Deterministic PR hygiene checks passed. |
Collaborator
Author
|
@codex security review |
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
This file contains hidden or 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
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.
Summary
Build the approved 2.91.0 release line with the three compatibility fixes already deployed on the server: list stored Codex pool accounts when the native home is absent, accept ingress-validated Hub bearer admission for search, and remember a validated dashboard admin login for one year.
This carries the original commits and authorship from #1, #3, and the remembered-login source used by #12. Version mirrors advance once per feature (2.91.1, 2.91.2, 2.91.3) on the fixed
releases/v2.91.0branch. It also carries the previously merged fork release/PR-target policy required to validate that branch. The runtime dependency lockfiles remain at upstream 2.91.0.The GUI behavior matches the deployed source change; its existing login form evidence is shown here:
Verification
bun run typecheck: passed.cd gui && bun test --isolate tests: 3,507 passed, zero failures.bun run structure:check,bun run privacy:scan, PR-target policy tests,bun run prepare:package, and four-file version synchronization check: passed.git diff --check: passed.The full runtime suite is left to PR CI under the documented shared-host resource exception. Focused runtime tests cover the two changed admission/account paths, unsafe and missing homes, credential preservation, denied credentials/scopes, correct stored-account selection, and preventing Hub keys from being forwarded. The full GUI suite covers the remembered-token expiry, validation, logout, origin isolation, and stale-response behavior. No production activation occurs before this PR and the upstream-sync prerequisite are reviewed and merged.
Checklist
Co-authored-by: Alex aleks00799@gmail.com
Co-authored-by: Aleksei Chistiakov aleks00799@gmail.com
Co-authored-by: jack-o-mania aleks00799+jack@gmail.com
Co-authored-by: Codex codex@localhost