Skip to content

checkpoint: into wallentx/termux-target from release/0.129.0 @ 685f3524f4fe#95

Merged
wallentx merged 6 commits intowallentx/termux-targetfrom
checkpoint/wallentx_termux-target_from_release_0.129.0_685f3524f4fe
May 6, 2026
Merged

checkpoint: into wallentx/termux-target from release/0.129.0 @ 685f3524f4fe#95
wallentx merged 6 commits intowallentx/termux-targetfrom
checkpoint/wallentx_termux-target_from_release_0.129.0_685f3524f4fe

Conversation

@unemployabot
Copy link
Copy Markdown

@unemployabot unemployabot Bot commented May 6, 2026

Termux release checkpoint

  • Source branch: release/0.129.0
  • Source hash: 685f3524f4fe044c660f7b19d015f906e1c24b93
  • Destination branch: wallentx/termux-target
  • Remaining first-parent commits on source: 0

This PR carries release-train conflict fixes and follow-up changes back into the reusable Termux patch branch.

Release-only workflow files and metadata under .github were restored to the destination branch versions before opening this PR.

bolinfest and others added 6 commits May 5, 2026 23:33
## Why

openai#21255 changed the Linux sandbox fallback so Codex can use a bundled
`codex-resources/bwrap` executable when no suitable system `bwrap` is
available. That lookup is relative to the native Codex executable
returned by
`std::env::current_exe()`, as implemented in
[`bundled_bwrap.rs`](https://github.com/openai/codex/blob/9766d3d51cec885114b6d6c53a02e9efbaf87171/codex-rs/linux-sandbox/src/bundled_bwrap.rs#L83-L93).

The release already publishes a separate `bwrap` DotSlash output, but
the Linux `codex` DotSlash output still pointed at a single-binary
`.zst` payload. Running the `codex` DotSlash manifest only materializes
the native `codex` executable; it does not also create sibling files
from the separate `bwrap` manifest. The fallback path therefore needs
the Linux `codex` DotSlash artifact itself to include the real `bwrap`
executable at `codex-resources/bwrap`.

## What changed

- stage a Linux primary `codex-<target>-bundle.tar.zst` release artifact
containing `codex` and `codex-resources/bwrap`
- point the Linux `codex` DotSlash outputs at that bundle tarball
- leave the standalone `bwrap` DotSlash output in place for consumers
that want to fetch `bwrap` directly

## Verification

- `jq . .github/dotslash-config.json`
- Ruby YAML parse of `.github/workflows/rust-release.yml`
…nt/wallentx_termux-target_from_release_0.129.0_685f3524f4fe

# Conflicts:
#	.github/workflows/rust-release.yml
#	.github/workflows/shell-tool-mcp.yml
#	codex-rs/Cargo.toml
#	scripts/termux-create-checkpoint-pr.sh
@unemployabot unemployabot Bot requested a review from wallentx May 6, 2026 11:17
@unemployabot unemployabot Bot added checkpoint Checkpoint merge termux-release Termux release automation labels May 6, 2026
@wallentx wallentx merged commit 3d1b115 into wallentx/termux-target May 6, 2026
1 check passed
@wallentx wallentx deleted the checkpoint/wallentx_termux-target_from_release_0.129.0_685f3524f4fe branch May 6, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

checkpoint Checkpoint merge termux-release Termux release automation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants