feat: split codex-common into smaller utils crates #11422
Merged
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.
We are removing feature-gated shared crates from the
codex-rsworkspace.codex-commongrouped several unrelated utilities behind[features], which made dependency boundaries harder to reason about and worked against the ongoing effort to eliminate feature flags from workspace crates.Splitting these utilities into dedicated crates under
utils/aligns this area with existing workspace structure and keeps each dependency explicit at the crate boundary.What changed
codex-rs/common(codex-common) from workspace members and workspace dependencies.codex-rs/utils/:codex-utils-clicodex-utils-elapsedcodex-utils-sandbox-summarycodex-utils-approval-presetscodex-utils-osscodex-utils-fuzzy-matchcodex-commoninto these crates (with tests), and added matchingBUILD.bazeltargets.codex-common:codex-rs/clicodex-rs/tuicodex-rs/execcodex-rs/app-servercodex-rs/mcp-servercodex-rs/chatgptcodex-rs/cloud-taskscodex-common.