Skip to content

release: codewith 0.1.92 - #589

Merged
andrei-hasna merged 1 commit into
mainfrom
release/codewith-0.1.92-remote-compaction
Aug 13, 2026
Merged

release: codewith 0.1.92#589
andrei-hasna merged 1 commit into
mainfrom
release/codewith-0.1.92-remote-compaction

Conversation

@andrei-hasna

@andrei-hasna andrei-hasna commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Summary

Prepare the next Codewith patch release for the merged remote-compaction hotfix in #588.

  • bump the Rust workspace and lockfile package versions from 0.1.91 to 0.1.92
  • add the 0.1.92 changelog entry for Responses v2 remote compaction routing
  • keep product implementation unchanged from merged main commit 9d91a48

Validation

  • python3 -m unittest codex-cli/scripts/test_build_npm_package.py
  • git diff --check
  • staged gitleaks protect --staged --redact -v

Publishing is intentionally not performed by this PR. It requires the independent release-candidate review GO and the normal publish-intent gate.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Prepare the remote-compaction hotfix for the 0.1.92 release.

Agent: agent-chief-engineering
@andrei-hasna

Copy link
Copy Markdown
Contributor Author

[REVIEW] GO — #589 @ fc5d880 — lens: correctness+security+gates, reviewer unresolved-account002 (1 of 1)

Reviewed the exact candidate against origin/main at 9d91a48.

What I read and ran:

  • git log --oneline origin/main..HEAD — exit 0; one release commit, fc5d880.
  • git diff origin/main...HEAD --stat — exit 0; CHANGELOG.md, codex-rs/Cargo.toml, and codex-rs/Cargo.lock only.
  • Full diff of all three changed files plus surrounding release workflow, package-builder, workspace-manifest, and remote-compaction sources — read successfully.
  • git diff --check origin/main...HEAD — exit 0; no whitespace errors.
  • bun install — exit 0; setup only, not a test gate.
  • package.json script inspection — exit 0; no test script and no typecheck script. This repository declares no test gate and no typecheck gate.
  • Forge gate read: gh pr view 589 --repo hasna/codewith --json statusCheckRollup — exit 0. A capability-safe projection of the same rollup was used for the evidence below.

Forge checks read (conclusion; IN_PROGRESS checks have an empty conclusion):

  • Bazel test on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
  • cla — SUCCESS
  • Check for spelling errors — SUCCESS
  • Blob size policy — SUCCESS
  • cargo-deny — SUCCESS
  • build-test — SUCCESS
  • Build Codewith Linux CLI — SUCCESS
  • Detect changed areas — SUCCESS
  • python-sdk — SUCCESS
  • metadata — SUCCESS
  • Bazel test on ubuntu-24.04 for x86_64-unknown-linux-musl — SUCCESS
  • sdks — IN_PROGRESS (conclusion empty)
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 1/4 — SUCCESS
  • Format / etc — SUCCESS
  • Build release x86_64-unknown-linux-gnu — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 2/4 — SUCCESS
  • Build ptrcomp-sandbox x86_64-unknown-linux-gnu — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 3/4 — SUCCESS
  • Build release aarch64-unknown-linux-gnu — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 4/4 — SUCCESS
  • Build ptrcomp-sandbox aarch64-unknown-linux-gnu — SUCCESS
  • Build release x86_64-apple-darwin — SUCCESS
  • Build ptrcomp-sandbox x86_64-apple-darwin — SUCCESS
  • Build release aarch64-apple-darwin — SUCCESS
  • Build ptrcomp-sandbox aarch64-apple-darwin — SUCCESS
  • Build release x86_64-unknown-linux-musl — SUCCESS
  • Build ptrcomp-sandbox x86_64-unknown-linux-musl — SUCCESS
  • Build release aarch64-unknown-linux-musl — SUCCESS
  • Build ptrcomp-sandbox aarch64-unknown-linux-musl — SUCCESS
  • Build ptrcomp-sandbox x86_64-pc-windows-msvc from source — IN_PROGRESS (conclusion empty)
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm (native main) — SKIPPED
  • cargo shear — SUCCESS
  • Build ptrcomp-sandbox aarch64-pc-windows-msvc from source — IN_PROGRESS (conclusion empty)
  • Argument comment lint package — SKIPPED
  • Bazel clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
  • Bazel clippy on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
  • Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
  • Argument comment lint - Linux — SUCCESS
  • Verify release build on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
  • Argument comment lint - Windows — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
  • CI results (required) — SUCCESS
  • [code]smith — SKIPPED

Current forge count: 43 total; 38 SUCCESS, 3 SKIPPED, 0 FAILURE, 0 CANCELLED, 2 IN_PROGRESS.

Blocking P0/P1 findings: none. The release-only candidate consistently bumps the workspace version to 0.1.92, updates the generated internal lockfile versions, and adds matching changelog notes for #588. The package builder explicitly rewrites the staged npm package version from the workspace/release version, so codex-cli/package.json remaining at its template version is not a release defect.

Non-blocking follow-up: package.json declares no test gate and no typecheck gate. I did not invent either gate or block on a command the repository does not declare. Merge is deferred only until the two named forge checks reach terminal success.

@andrei-hasna

Copy link
Copy Markdown
Contributor Author

[REVIEW] GO — #589 @ fc5d880 — lens: correctness+security+gates, reviewer unresolved-account002 (1 of 1)

Reviewed the exact candidate against fetched origin/main at 9d91a48.

What I read:

  • git log --oneline origin/main..HEAD — exit 0; one release commit, fc5d880.
  • git diff origin/main...HEAD --stat — exit 0; three changed files: CHANGELOG.md, codex-rs/Cargo.toml, codex-rs/Cargo.lock.
  • Full diff of every changed file, including the complete Cargo.lock version-only diff, plus surrounding workspace-version, release workflow, package-builder, and package-version source.
  • package.json — exit 0; no test script and no typecheck script.

Commands and gates:

  • bun install — exit 0; setup only, not a repository gate.
  • This repository declares no test gate. No typecheck gate is declared. I did not invent either gate.
  • gh pr view 589 --repo hasna/codewith --json statusCheckRollup — exit 0; 43 checks read: 38 SUCCESS, 3 SKIPPED, 0 FAILURE, 0 CANCELLED, and 2 IN_PROGRESS. The in-progress checks have an empty conclusion.
  • The lane's chosen command git diff --check origin/main...HEAD — exit 0; 0 whitespace errors. This is not a repository-declared gate.
  • The lane's chosen command python3 .github/scripts/verify_cargo_workspace_manifests.py — exit 0; 0 reported manifest errors. This is not a repository-declared gate.

Forge check conclusions read from the rollup:

  • Bazel test on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
  • cla — SUCCESS
  • Check for spelling errors — SUCCESS
  • Blob size policy — SUCCESS
  • cargo-deny — SUCCESS
  • build-test — SUCCESS
  • Build Codewith Linux CLI — SUCCESS
  • Detect changed areas — SUCCESS
  • python-sdk — SUCCESS
  • metadata — SUCCESS
  • Bazel test on ubuntu-24.04 for x86_64-unknown-linux-musl — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 1/4 — SUCCESS
  • Format / etc — SUCCESS
  • sdks — SUCCESS
  • Build release x86_64-unknown-linux-gnu — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 2/4 — SUCCESS
  • Build ptrcomp-sandbox x86_64-unknown-linux-gnu — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 3/4 — SUCCESS
  • Build release aarch64-unknown-linux-gnu — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 4/4 — SUCCESS
  • Build ptrcomp-sandbox aarch64-unknown-linux-gnu — SUCCESS
  • Build release x86_64-apple-darwin — SUCCESS
  • Build ptrcomp-sandbox x86_64-apple-darwin — SUCCESS
  • Build release aarch64-apple-darwin — SUCCESS
  • Build ptrcomp-sandbox aarch64-apple-darwin — SUCCESS
  • Build release x86_64-unknown-linux-musl — SUCCESS
  • Build ptrcomp-sandbox x86_64-unknown-linux-musl — SUCCESS
  • Build release aarch64-unknown-linux-musl — SUCCESS
  • Build ptrcomp-sandbox aarch64-unknown-linux-musl — SUCCESS
  • Build ptrcomp-sandbox x86_64-pc-windows-msvc from source — IN_PROGRESS (conclusion empty)
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm (native main) — SKIPPED
  • cargo shear — SUCCESS
  • Build ptrcomp-sandbox aarch64-pc-windows-msvc from source — IN_PROGRESS (conclusion empty)
  • Argument comment lint package — SKIPPED
  • Bazel clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
  • Bazel clippy on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
  • Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
  • Argument comment lint - Linux — SUCCESS
  • Verify release build on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
  • Argument comment lint - Windows — SUCCESS
  • Bazel test on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
  • CI results (required) — SUCCESS
  • [code]smith — SKIPPED

Blocking P0/P1 findings: none. The release-only candidate consistently bumps the workspace version to 0.1.92, updates matching internal lockfile package versions, and adds the release changelog entry for the remote-compaction fix. The package builder reads the workspace/release version and rewrites staged npm package metadata, so the template package version remaining in codex-cli/package.json is not a defect in this release candidate.

Non-blocking follow-up: the repository declares no test or typecheck gate. Two forge checks are still IN_PROGRESS; their current status is recorded above and does not constitute a code finding.

@andrei-hasna
andrei-hasna merged commit 871cb28 into main Aug 13, 2026
43 of 44 checks passed
@andrei-hasna
andrei-hasna deleted the release/codewith-0.1.92-remote-compaction branch August 13, 2026 18:04
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 13, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant