Skip to content

Integration: drift check and upstream rust-v0.162.1 fixes (WI-1125) - #33

Merged
thedancingdeveloper merged 5 commits into
fork/mainfrom
integrate/codex-next
Oct 15, 2026
Merged

thedancingdeveloper merged 5 commits into
fork/mainfrom
integrate/codex-next

Conversation

@thedancingdeveloper

Copy link
Copy Markdown

The integration PR for the fork, carrying two reviewed items:

Merging publishes a fork-<sha> release, built on the GCP rust-heavy runner. vogt-dev pins it for the WI-1150 parity re-run.

🤖 Generated with Claude Code

thedancingdeveloper and others added 5 commits October 15, 2026 14:07
A scheduled workflow fails when a newer stable rust-vX.Y.Z tag has shipped
than the one recorded in FORK.md and stamped in fork-release.yml, or when the
carried-patch table grows past ten rows. It reports; the rebase stays the
runbook. The first run finds drift: the fork records rust-v0.162.0 and the
newest stable tag is rust-v0.162.1.
GitHub runs schedule only from the default branch, which is the upstream
mirror, so the cron could never fire. The check now passes when FORK.md's
"Upstream fixes taken through" marker equals the newest stable tag, kept
separate from the rebase base.
…penai#52648)

## Why

A running shared background server owns its feature settings until it restarts. Differences from a client's configuration files or defaults should not trigger a compatibility warning or a restart request.

## What changed

- Check shared-service features only when explicitly overridden on the command line.
- Exclude overrides superseded by active legacy managed configuration or feature requirements, while supporting older servers without `configRequirements/read`.
- Pass only the remaining explicit feature overrides to a requested daemon restart.

## Testing

Update compatibility tests for stale daemon overrides, explicit enable/disable requests, managed configuration, and older servers. Extend CLI startup tests to verify the feature overrides persisted after a restart.

GitOrigin-RevId: ac92c9c02cd70fa233203ebef1182fd119325dd1
(cherry picked from commit d3f9b22)
…1866)

## Why

Rendering an entire question title as one terminal line removes line endings and misaligns hyperlink source ranges with the visible text.

## What changed

Wrap and annotate each logical line of asynchronous question titles separately, preserving blank lines and handling both LF and CRLF endings while retaining complete hyperlink destinations.

## Testing

Add a rendering regression test and snapshot covering multiline titles with code fences, Unicode text, and a URL. Check LF and CRLF rendering equivalence and hyperlink destinations at narrow and wide widths.

GitOrigin-RevId: ccd7256dbaed91ce98374e52b17d3a1b87645574
(cherry picked from commit eef4719)
…s, preserving line breaks and complete hyperlink destinations. (openai#51866)

- Fixed startup failures caused by differences between a running background server's feature settings and CLI defaults. Compatibility checks now apply only to explicit command-line feature overrides. (openai#52648)

Full Changelog: openai/codex@rust-v0.162.0...rust-v0.162.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants