[github-actions]

Summary

2.96.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.97.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.96.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.

[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: 007dbfd
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 13b6584b-7e11-4581-a9ef-dade526039f7

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

[lidge-jun]

Maintainer integration (MAINTAINERS.md dev exception) for the 2.96.0 release pre-move.

• Exact head: f3acd315740eeb3db6a72c4346f01defcca8c3b2 (parent: dev tip 007dbfd895, the frozen 2.96.0 candidate), opened by dev-version-bump.yml run 41266128972 (success), which proved 2.96.0 has no tag or npm publication and ran tests/ci-workflows/release-version-line.test.ts for 2.97.0.
• Diff: version line only in the 4 release version sources (2.96.0 -> 2.97.0).
• PRs opened with GITHUB_TOKEN do not trigger pull_request workflows, so there is no PR CI on this head; same handling as chore(release): open dev at 2.96.0 before releasing 2.95.0 #8033 for 2.95.0 and chore(release): open dev at 2.95.0 before releasing 2.94.0 #7934 for 2.94.0. release.yml independently refuses publication until dev outranks 2.96.0.