Skip to content

[codex] import token_data from codex-login directly#15903

Merged
bolinfest merged 1 commit intomainfrom
pr15903
Mar 26, 2026
Merged

[codex] import token_data from codex-login directly#15903
bolinfest merged 1 commit intomainfrom
pr15903

Conversation

@bolinfest
Copy link
Copy Markdown
Collaborator

@bolinfest bolinfest commented Mar 26, 2026

Why

token_data is owned by codex-login, but codex-core was still re-exporting it. That let callers pull auth token types through codex-core, which keeps otherwise unrelated crates coupled to codex-core and makes codex-core more of a build-graph bottleneck.

What changed

  • remove the codex-core re-export of codex_login::token_data
  • update the remaining codex-core internals that used crate::token_data to import codex_login::token_data directly
  • update downstream callers in codex-rs/chatgpt, codex-rs/tui_app_server, codex-rs/app-server/tests/common, and codex-rs/core/tests to import codex_login::token_data directly
  • add explicit codex-login workspace dependencies and refresh lock metadata for crates that now depend on it directly

Validation

  • cargo test -p codex-chatgpt --locked
  • just argument-comment-lint
  • just bazel-lock-update
  • just bazel-lock-check

Notes

  • attempted cargo test -p codex-core --locked and cargo test -p codex-core auth_refresh --locked, but both ran out of disk while linking codex-core test binaries in the local environment
@bolinfest bolinfest changed the title refactor: stop re-exporting token_data from codex-core Mar 26, 2026
@bolinfest bolinfest requested a review from aibrahim-oai March 26, 2026 19:42
@bolinfest bolinfest marked this pull request as ready for review March 26, 2026 19:42
@bolinfest bolinfest changed the title [codex] stop re-exporting token_data from codex-core Mar 26, 2026
@bolinfest bolinfest merged commit b23789b into main Mar 26, 2026
36 of 37 checks passed
@bolinfest bolinfest deleted the pr15903 branch March 26, 2026 20:34
@github-actions github-actions bot locked and limited conversation to collaborators Mar 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

2 participants