Repository navigation
chore(release): open dev at 2.75.0 before releasing 2.74.0 - #6317
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: lidge-jun/opencodex/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
Maintainer integration (MAINTAINERS.md, 2026-09-06 policy): @lidge-jun ( |
Summary
2.74.0is about to be released. Merging this first meansdevalready outranks the new tag when it lands, so neitherdevnor any open pull request ever inherits the version-line failure.release.ymlrefuses to publish until this has merged.This moves
devto2.75.0inpackage.jsonand the desktop versionsources (
tauri.conf.json,Cargo.toml, and theopencodex-desktopentry ofCargo.lock).Opened automatically by
.github/workflows/dev-version-bump.yml. The sameversion-line move was previously done by hand in 32529c2, e4a85d1, 076ad30, and
befcac3.
Verification
The workflow proved
2.74.0has neither a Git tag nor an npm publication, andbun test tests/ci-workflows/release-version-line.test.tsproved the chosen development version is unused.Checklist