[WRONG BRANCH] release: v2.28.0

[lidge-jun]

Summary

Version bump to 2.28.0 on main, produced by scripts/release.ts 2.28.0 --publish. One line changes: package.json version.

The helper wants to push this commit to main directly; branch protection requires a pull request, so this PR carries the same commit (ce4e05dde) it would have pushed. Once merged, the helper is re-run from a main checkout at that SHA — it treats the bump as a desired end state, finds package.json already at 2.28.0, reuses the existing release commit, and proceeds to the CI wait and the workflow dispatch.

Verification

The helper's full local gate ran to completion at 5bdf56077 before producing this commit:

• bun run audit:high — clean
• bun x tsc --noEmit — clean
• bun test --isolate tests — 13737 pass, 0 fail, 866 files, 509s
• bun run privacy:scan — passed
• Release metadata preflight: 2.28.0 is unused on npm and moves the latest channel forward from 2.27.0

Cross-platform CI is green at the parent commit 5bdf56077 (32347982184) and Service lifecycle passed there too (32347982293). This PR adds no source change on top of that, so the release SHA's own push run is the one that gates the publish.

Version reasoning is in #2186: one user-visible feature (Logs intercepted-helper attribution) plus provider behaviour changes across xAI, Anthropic, Google, and the capability gate — new behaviour on upgrade, not only fixes.

Checklist

• Tests added or updated (n/a — version bump only)
• bun run typecheck passes
• Full suite passes (13737/13737 locally, plus green CI at the parent)
• Docs updated if user-facing behavior changed (n/a)

Summary by CodeRabbit

• Chores
  • Updated the application version from 2.27.0 to 2.28.0.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
Automatic draft conversion failed (token cannot change draft status). Please convert this pull request to a draft manually. The required enforce-target check will keep failing until every issue above is resolved.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f7fa499e-c77c-40a8-bd19-1a20a432c8b4

📥 Commits

Reviewing files that changed from the base of the PR and between 5bdf560 and ce4e05d.

📒 Files selected for processing (1)

• package.json

Included review availability: Your plan provides up to 10 included reviews per hour; 5 remain after this review.

---

📝 Walkthrough

Walkthrough

The package version in package.json changes from 2.27.0 to 2.28.0.

Changes

Package version update

Layer / File(s)	Summary
Update package version package.json	Line 3 changes the package version from 2.27.0 to 2.28.0.

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

Merge Risk: ⚪ Minimal · up to ce4e0

This PR only updates the package version, with the supplied checks passing and no actionable merge-blocking risk remaining.

Possibly related PRs

• lidge-jun/opencodex#2136: This PR also updates the package version in package.json.

Suggested labels: chore

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 and version bump to v2.28.0, which matches the pull request's main change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-2.28.0

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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