Version metadata still says 0.6.0-alpha.2 on latest main #169

Ran into a version mismatch while checking my self-hosted install.

I updated to the latest main / latest release tag, which looks like v0.7.0-alpha.4, but the app still reports 0.6.0-alpha.2.

Two things:

• /api/health reports 0.6.0-alpha.2
• Several version files in the repo still have 0.6.0-alpha.2

Files I found with the old version:

• static/version.json
• pyproject.toml
• desktop/package.json
• desktop/src-tauri/Cargo.toml
• desktop/src-tauri/tauri.conf.json
• desktop/src-tauri/Cargo.lock
• uv.lock, as 0.6.0a2

I didn't find 0.7.0-alpha.4 hardcoded anywhere in the repo itself. The latest version seems to only exist in the GitHub release/tag.

Looked around a little more and found what might explain it. There used to be a version-bump workflow that committed the release version back to main, with a note that self-hosted users would get the correct version after a plain git pull.

That workflow was later removed in favor of the macOS/Windows release workflows patching the version files at build time. That probably works fine for packaged desktop releases, but it looks like source/Docker/self-hosted installs don't get that build-time version stamping step.

Checked the tags too, and every tag from v0.6.0-alpha.3 through v0.7.0-alpha.4 still has 0.6.0-alpha.2 in static/version.json, pyproject.toml, and desktop/src-tauri/Cargo.lock.

So it looks like the release is v0.7.0-alpha.4, but self-hosted installs from source still report 0.6.0-alpha.2.

Not sure if the intended fix is to bring back the version-bump workflow, make Docker/source builds derive the version from git tags, or something else. Just wanted to flag it since it makes a current self-hosted install look like it's still on an older version.