chore: set version to 0.3.0 across all sources (+ drop v0.4 references)

[debpalash]

The current/upcoming version is v0.3.0 (0.2.7 is the prior stable). Two parts:

1. Version → 0.3.0 everywhere (consistency)

The app even reported a phantom 0.4.0 in main.py/marketplace metadata. Now every source reads 0.3.0:

• pyproject.toml, frontend/src-tauri/Cargo.toml, frontend/src-tauri/tauri.conf.json, frontend/package.json
• backend/main.py (FastAPI version) + marketplace.py export metadata
• CHANGELOG.md: [0.2.7] — Unreleased → [0.3.0] — Unreleased
• uv.lock + Cargo.lock reconciled (1 line each) so uv sync --frozen / cargo --frozen in the bootstrap + CI still hold. uv lock --check passes.

This is the in-code dev version; the git tag still happens later per the release cadence (when you call it "actually useful").

2. Drop stray v0.4 references

Reworded the v0.4 deferral comments in errorDocsMap.ts, indextts/bootstrap.py, _secret_key.py, and the troubleshooting.md notarization line — no forbidden version chatter left in live code.

Verified: no v0.4 in live code; backend parses; frontend typecheck OK; lockfiles consistent.

Out of scope: ~90 historical v0.4 notes under .planning/ (superseded phase records) — left as-is.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Bumped application and bundle version metadata to 0.3.0 across the project and unified runtime version sourcing.

• Documentation

  • Revised supply-chain/hardening timeline notes and clarified macOS Gatekeeper notarization troubleshooting.

• Tests

  • Added assertions ensuring the runtime app version is a valid semantic version and matches the packaged version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0e2f2bda-f892-4a41-bba2-944e2b73720a

📥 Commits

Reviewing files that changed from the base of the PR and between 419227a and 27310b7.

📒 Files selected for processing (4)

• backend/api/routers/marketplace.py
• backend/core/version.py
• backend/main.py
• tests/test_app_version.py

✅ Files skipped from review due to trivial changes (1)

• backend/api/routers/marketplace.py

---

📝 Walkthrough

Walkthrough

Introduce a runtime APP_VERSION (sourced from installed package metadata) and use it for FastAPI and marketplace bundle metadata; bump project/frontend/Tauri manifests and changelog to 0.3.0; reword docstrings/comments and add a test asserting version consistency.

Changes

Version and documentation harmonization

Layer / File(s)	Summary
Application and bundle metadata backend/core/version.py, backend/main.py, backend/api/routers/marketplace.py, pyproject.toml, frontend/package.json, frontend/src-tauri/Cargo.toml, frontend/src-tauri/tauri.conf.json, CHANGELOG.md	Add APP_VERSION resolved from installed package metadata and use it for FastAPI version and .omnivoice bundle omnivoice_version; bump project and frontend manifest version fields and changelog header to 0.3.0.
Docstrings and troubleshooting text backend/engines/indextts/bootstrap.py, backend/services/_secret_key.py, docs/install/troubleshooting.md, frontend/src/utils/errorDocsMap.ts	Rephrase threat-model/docstring notes, key-decision reference text, macOS Gatekeeper cause wording, and TypeScript header comments to reference deferred hardening/decision notes rather than prior version-based labels.
Version consistency test tests/test_app_version.py	Add test validating core.version.APP_VERSION matches the installed omnivoice package version and is semver-like.

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs:

• debpalash/OmniVoice-Studio#143: Related macOS notarization/signing work and docs changes referencing release.yml and Apple certificate secrets.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 40.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	The PR description comprehensively covers the changes but lacks explicit testing details and some checklist items required by the template.	Add explicit testing details (local testing, smoke-matrix CI validation), confirm all version file syncs, and check off relevant checklist items from the template.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly summarizes the PR's main objective: updating the version to 0.3.0 across all sources and removing stray v0.4 references.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/drop-v0.4-references

---

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 and usage tips.}

[greptile-apps]

Greptile Summary

This PR bumps every version string in the project from 0.2.7 (and the stray 0.4.0 phantom) to 0.3.0, and resolves the prior reviewer finding by introducing backend/core/version.py — a single runtime source of truth that reads from installed package metadata rather than hard-coded literals.

• Version consistency sweep: pyproject.toml, Cargo.toml, tauri.conf.json, package.json, uv.lock, and Cargo.lock all updated to 0.3.0; both marketplace.py export sites and main.py's FastAPI version= now reference APP_VERSION from core.version.
• Stale comment cleanup: v0.4 deferral notes in errorDocsMap.ts, bootstrap.py, _secret_key.py, and troubleshooting.md reworded to version-agnostic language.
• Test coverage added: tests/test_app_version.py asserts that APP_VERSION is a valid semver string and equals the installed package metadata, guarding against future literal drift.

Confidence Score: 5/5

Safe to merge — this is a mechanical version bump with a well-scoped refactor to eliminate hard-coded version literals.

All changes are version string updates and comment rewording; the new core/version.py correctly reads from installed package metadata, both marketplace export sites use the shared constant, and lockfiles are reconciled.

backend/core/version.py — the fallback literal will need a manual update on each future version bump unless replaced with a pyproject.toml read.

Important Files Changed

Filename	Overview
backend/core/version.py	New single-source-of-truth module reading version from importlib.metadata; fallback literal "0.3.0" will drift on next bump.
tests/test_app_version.py	New tests asserting APP_VERSION is semver and matches installed package metadata; designed for synced environments only.
backend/main.py	APP_VERSION import added mid-file (after lifespan function) instead of at top of module with other imports.
backend/api/routers/marketplace.py	Both omnivoice_version literals replaced with APP_VERSION — addresses the stale-string issue from the prior review thread.
pyproject.toml	Version bumped from 0.2.7 to 0.3.0; remains the single source of truth for the installed package metadata.
uv.lock	Lockfile reconciled to 0.3.0 so uv sync --frozen / uv lock --check passes in CI.
frontend/src-tauri/Cargo.lock	Cargo lockfile updated to 0.3.0 for the omnivoice-studio package entry.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pyproject.toml\nversion = 0.3.0] -->|uv sync / install| B[Installed package\nomnivoice 0.3.0]
    B -->|importlib.metadata.version| C[core/version.py\nAPP_VERSION]
    A -->|fallback only if not installed| C
    C --> D[main.py\nFastAPI version=APP_VERSION]
    C --> E[marketplace.py\nomnivoice_version export]
    C --> F[marketplace.py\nomnivoice_version publish]
    C --> G[tests/test_app_version.py\nassert APP_VERSION == metadata]

Loading

_{Reviews (3): Last reviewed commit: "refactor(version): read app version from..." | Re-trigger Greptile}

[greptile-apps]

Want your agent to iterate on Greptile's feedback? Try greploops.