Repository navigation
Upgrade embedded Codex runtime to 0.167.0 - #559
Merged
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.
NeverWrite currently embeds Codex 0.166.0. Upgrade the embedded runtime to stable 0.167.0 (
086ccc833bc9cf01024ad2dd6af7dbd421b6bf9a), including every Codex dependency, the local PTY package, the committed lockfile, and packaging source checks. Both runtime executables use the same baseline.Adapt the ACP boundary to the new approval lifecycle:
HumanCommandcheckpoints with one-time approval, rejection, and cancellation options. Resolve their activity independently of the command execution.Retain NeverWrite's ACP v1 contracts and existing feature restrictions. V8 152.2.0, its pinned cppgc patch, verified artifact checksums, the Rust toolchain, and upstream PTY sources remain aligned. Update maintenance documentation and use 0.166.0 as the rollback baseline.
Validation on Linux x64:
Runtime smokes use isolated temporary state and a local Responses mock. Local runtime execution used debug builds; native macOS/Windows execution, signing, and full release packaging are covered by the existing package CI matrix.