[codex] Finish outdated and upgrade CLI parity#57
Merged
Conversation
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
outdatedandupgradeflags that were still marked unsupported in the native CLIoutdated --log-format jsonso existing automation keeps workingWhy
The native CLI still exposed a few parity gaps around
outdatedandupgrade:--log-leveland theoutdatedterminal dimension flags were still treated as unsupported even though they are part of the pinned upstream surfaceoutdated, the native logger emitted a custom{level,message}envelope instead of the upstream event schema, which could break existing JSON log consumersWhat Changed
outdated/upgradelogging flags and terminal dimensionsoutdatedandupgradethrough native command loggers so they emit filtered text logs, trace terminal dimensions when requested, and report lifecycle milestones during config loading, lockfile reads, and lockfile writestype, numericlevel,timestamp, andtextoutdated/upgradeno longer show these supported flags as unsupportedTODO_ARGS.mdentries and refreshed the parity inventory/dashboard so the compatibility docs now report full option coverage for the pinned upstream command surfacemake testsso this parity state stays enforced in local verificationUser Impact
devcontainer outdatednow accepts--log-level,--terminal-columns, and--terminal-rowsas supported native flagsdevcontainer upgradenow accepts--log-levelas a supported native flagdevcontainer outdated --log-format jsonreceive upstream-compatible event objects instead of a native-only schemaValidation
make tests