ci(desktop-release): auto-resolve the production version on merge to main

[bladehell-ai]

Problem

A push to main took desktop/package.json literally. If that version had already shipped, preflight set should_release=false, all three build jobs were skipped, and the merge produced no release at all — silently, with nothing failing.

desktop/package.json is at 1.0.43 while production is on v1.0.46, so every merge to main since 1.0.43 has been a no-op release. Shipping meant committing a version bump to develop and merging to main a second time.

Changes

1. main resolves the version itself (preflight)

A push to main now runs the same "bump patch until unreleased" loop develop already had, so a develop→main merge always ships:

BASE=1.0.43 → v1.0.43 shipped → 1.0.44 → … → 1.0.47 unreleased → release v1.0.47

An explicit workflow_dispatch version is still taken literally and still skipped if that release exists, so a number can be pinned by hand.

Tags don't collide: v1.0.47 and v1.0.47-dev.2 are distinct refs, and semver sorts the prerelease below the release — the same property the dev channel's existing comment relies on. Promoting the version the dev channel has been building is the intended outcome.

2. New bump-develop-version job

After a successful production build, writes the next patch after the shipped version into desktop/package.json on develop, so the committed number tracks reality instead of drifting.

• Never moves the version backwards (a hand-set 1.1.0 on develop is left alone)
• No-ops when already correct
• Rebase-retries if develop moved mid-run
• Pushes to develop, never main — a bot commit touching desktop/** on main would retrigger this workflow and immediately release the bumped version. [skip ci] is a second guard; a GITHUB_TOKEN push doesn't trigger workflows anyway.

Effect on the next release

Merging develop → main releases v1.0.47 and then sets develop to 1.0.48. No manual bump commit.

Verification

Workflow YAML parses (8 jobs resolve). The backwards-guard comparison was tested against current values of 1.0.43 / 1.0.48 / 1.1.0 / 1.0.47. desktop/package.json has no version/preversion lifecycle scripts, so npm version --no-git-tag-version is a plain file write.

🤖 Generated with Claude Code