Palash Debnath
5cab8e0149
Renames what users see. The app, the installers, the window title, the
docs and all 21 locales now say VoiceStudio, with "(previously
OmniVoice-Studio)" noted near the title of each doc surface so people
recognise it.
Deliberately NOT renamed, because renaming any of them silently breaks
an existing install — there is no legacy-path fallback anywhere in this
codebase:
- bundle identifier com.debpalash.omnivoice-studio (MSI UpgradeCode,
macOS TCC grants, managed venv, WebView localStorage, the
single-instance lock)
- data directories OmniVoice / .omnivoice and omnivoice.db
- the ~150 OMNIVOICE_* environment variables
- the X-OmniVoice-* HTTP headers (a wire protocol)
- the published Docker image paths
- the OmniVoice ENGINE, which is a model name and not this product
tests/test_identity_paths_survive_the_rename.py pins every one of those
so a future well-meaning sweep cannot orphan a user's library.
Linux .deb users install a new package name and should apt remove
omnivoice-studio; that note is in the changelog.
1.2 KiB
1.2 KiB
Summary
Changes
Type
- 🐛 Bug fix
- ✨ New feature
- ♻️ Refactor
- 📝 Documentation
- 🧪 Tests
- 🔧 CI / Build
- 🚀 Release prep
Testing
Checklist
- I've tested this locally
- I've updated relevant documentation (if applicable)
- No local machine paths, logs, or personal env details in this PR
- Version files are in sync (if version bump):
pyproject.toml,package.json,tauri.conf.json,Cargo.toml - If this PR changes runtime behavior, the regression fixture at
tests/fixtures/omnivoice_data/still loads green on thesmoke-matrixCI job (macOS + Windows + Linux)
Release cadence
VoiceStudio ships continuous-to-main — no release candidates, no soak windows.
Every merged PR is immediately part of the rolling preview (main, Docker
:latest, the desktop Preview channel). Versioned releases are tagged from
main when it's ready; main then bumps to the next patch automatically.
Users who want stability pin a release tag / Docker :stable / the desktop
Stable channel.