[github-actions]

Summary

2.91.0 is about to be released. Merging this first means dev already outranks the new tag when it lands, so neither dev nor any open pull request ever inherits the version-line failure. release.yml refuses to publish until this has merged.

This moves dev to 2.92.0 in package.json and the desktop version
sources (tauri.conf.json, Cargo.toml, and the opencodex-desktop entry of Cargo.lock).

Opened automatically by .github/workflows/dev-version-bump.yml. The same
version-line move was previously done by hand in 32529c2, e4a85d1, 076ad30, and
befcac3.

Verification

The workflow proved 2.91.0 has neither a Git tag nor an npm publication, and bun test tests/ci-workflows/release-version-line.test.ts proved the chosen development version is unused.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Review readiness checklist

This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:

• Required local validation passed; commands, results, and any full-suite exception are documented.

• I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).

• I resolved all correct Codex and CodeRabbit findings.

• My PR is ready for review.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Source mode: Auto
• Repository: lidge-jun/opencodex
• Branch: dev
• File: .coderabbit.yaml
• Commit: 1025acd
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: fb97b3e1-a1fa-412f-a2e5-55b0e95dcece

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}

[github-actions]

⏳ DRAFT

• hygiene: unsponsored_surface.

What to do

• Fix unsponsored_surface — This changes an authentication, workflow, release-automation, or dependency surface. MAINTAINERS.md requires security review for these; ask a maintainer to apply maintainer-sponsored once they have reviewed it. Paths: package.json.
• Tick all four boxes in the PR description once you're done (currently 0/4).

Review readiness checklist

• ⬜ Required local validation passed; commands, results, and any full-suite exception are documented.
• ⬜ I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).
• ⬜ I resolved all correct Codex and CodeRabbit findings.
• ⬜ My PR is ready for review.

0/4 boxes ticked.

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.

[lidge-jun]

Merged with owner authority per maintainer decision 2026-10-23 (jun): the project owner authorized the 2.91.0 release on the documented owner path (--admin, as in #7475), because no second-maintainer approval is available for this mechanical pre-move.

Exact-head verification on 74813c621b7c363e190e19adde8f53e017965af5: against dev 1025acd4b1 (the frozen 2.91.0 candidate) the diff is the four version sources only (package.json, desktop tauri.conf.json, Cargo.toml, Cargo.lock; 2.91.0 → 2.92.0). The dev-version-bump run that opened it: 39807442943. The candidate itself passed Cross-platform CI lane=all 39798671504 and Service lifecycle 39807438208. Promotion #7530 follows this merge.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-22T16:07:02.975906Z	74813c6	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.