Skip to content

release: prepare OpenCodex v1.3.2 - #196

Open
MisterWanted wants to merge 1 commit into
mainfrom
release/1.3.2-campaign-20260906
Open

release: prepare OpenCodex v1.3.2#196
MisterWanted wants to merge 1 commit into
mainfrom
release/1.3.2-campaign-20260906

Conversation

@MisterWanted

@MisterWanted MisterWanted commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Prepare @groeponline/opencodex 1.3.2 from the current main integration line.
  • Includes only the package version change; the already-merged Kimi compatibility, telemetry and test-isolation changes are the release payload.
  • Does not include unapproved client-artifact or Claude-admission PRs. Publication, container creation, deployment and live revision verification are separate gates after this PR is approved and merged.

Verification

  • bun install --frozen-lockfile: passed, lockfile unchanged.
  • bun run typecheck: passed.
  • bun run privacy:scan: passed.
  • Local main-runtime baseline is NOT GREEN: it hit the first seven-minute watchdog and a passthrough timing assertion. Missing GUI dependencies were also identified and installed with the frozen lockfile. The automatic second attempt was stopped to avoid extending host contention (eight threads, load around 32). No passing baseline is claimed; remote exact-head runtime CI remains required. The parallel adapter lane also hit both watchdog attempts.
  • Duplicate local pre-push execution was skipped for this draft task-branch upload after the recorded checks; no main, merge, publication or deployment gate was bypassed.
  • Version 1.3.2 absent from npm and Git tags at preparation preflight.

Linear

  • Issue: GRO2-1560 — existing OpenCodex release-convergence control, continued with current source/runtime evidence rather than creating a parallel release initiative.

Checklist

  • Scope stays focused and avoids unrelated cleanup.
  • No deployment or publication is implied by the package bump.
  • Maintainer release review and exact-head required checks complete.

Summary by CodeRabbit

  • Chores
    • Updated the package version from 1.3.1 to 1.3.2.

@coderabbitai

coderabbitai Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 93fb3cd2-595c-4084-86ae-7eb2466631fb

📥 Commits

Reviewing files that changed from the base of the PR and between 1e07891 and 093d331.

📒 Files selected for processing (1)
  • package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The package version in package.json was incremented from 1.3.1 to 1.3.2.

Changes

Package version update

Layer / File(s) Summary
Update package version
package.json:3
The package version changes from 1.3.1 to 1.3.2.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 093d3

This change prepares version 1.3.2 by updating package metadata only. No actionable merge risk is evident.

Suggested reviewers: ingwannu

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the release preparation and specifies version 1.3.2, which matches the package.json version change and the PR objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/1.3.2-campaign-20260906

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@MisterWanted
MisterWanted marked this pull request as ready for review September 7, 2026 01:08
@MisterWanted

Copy link
Copy Markdown
Contributor Author

Current release handoff: exact head 093d331 now has successful Cross-platform CI (run 34052773097), image build, security, actionlint, CodeFactor and Socket checks. This supersedes the earlier inconclusive local baseline only for the behavior exercised by CI. Marked ready for maintainer/release review and requested the documented maintainers. No approval, merge, tag, npm publication or deployment is implied. Production remains v1.3.1 at 81dd4ec. The existing release branch remains the single v1.3.2 candidate.

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.

1 participant