release: 0.5.6

[debpalash]

Version 0.5.5 → 0.5.6 (frontend/package.json, pyproject.toml, backend/core/version.py, plus the uv.lock/bun.lock self entries), and CHANGELOG.md [0.5.6] — 2026-09-23.

• Leads with integrations (Twilio calls; Claude Code / Cursor / Codex / OpenAI Agents SDK setup).
• 5 highlights, download table, upgrade notes (MCP /mcp/, /v1 400 errors, real MP3), Tauri migration, installer-trust note.
• Contributors and bug reporters verified from git log v0.5.5..main and the merged PRs (feat(longform): download a chapter cue sheet after a render #2278 co-author @Shivendra-Coherent included).

Checks: test_app_version, test_changelog_style, test_changelog_parse (25 passed); bun install --frozen-lockfile and uv lock --check pass.

🤖 Generated with Claude Code

The release updates version references to 0.5.6 and replaces the Unreleased changelog content with release notes dated 2026-09-23. Review the release notes and contributor credits before merge; no current review findings were supplied to assess release risks.

[greptile-apps]

The PR appears safe to merge with no concrete release-blocking issue identified.

Summary

The PR prepares release 0.5.6:

• Synchronizes maintained frontend, Python package, and backend fallback versions.
• Adds the 0.5.6 release notes, downloads, upgrade guidance, and contributor attribution.
• No merge-changing correctness, security, or repository-rule issue was identified.

_{Reviews (1) · Last reviewed commit: "release: 0.5.6"}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: debpalash/VoiceStudio/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: bbf6d8b5-d46a-4782-b699-a75a16083ddb

📥 Commits

Reviewing files that changed from the base of the PR and between 794d0f1 and c5ddad7.

⛔ Files ignored due to path filters (2)

• bun.lock is excluded by !**/*.lock, !**/*.lock, !**/bun.lock
• uv.lock is excluded by !**/*.lock, !**/*.lock, !**/uv.lock

📒 Files selected for processing (4)

• CHANGELOG.md
• backend/core/version.py
• frontend/package.json
• pyproject.toml

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

---

📝 Walkthrough

Walkthrough

The changelog adds a 0.5.6 release entry and updates release-related sections. The backend fallback version, frontend package version, and project version change from 0.5.5 to 0.5.6.

Changes

Release 0.5.6

Layer / File(s)	Summary
Release notes and version metadata pyproject.toml, frontend/package.json, backend/core/version.py, CHANGELOG.md	The project, frontend, and backend fallback versions change to 0.5.6. The changelog adds release notes, platform download links, upgrade and migration notes, highlights, contributors, and bug reporters.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: kevin9327, velixio

Merge Risk: ⚪ Minimal · up to c5dda

The release notes follow the tagged-release format, and the Tauri manifest remains intentionally unchanged. No actionable issue remains to block the release.

🚥 Pre-merge checks | ✅ 7 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title identifies a release version bump but does not use the required Conventional Commit format with a scope, and it does not include an issue reference. The repository requirement also states th…	Use an approved non-version-bump title with a scope and include the issue reference in the title or body, or obtain the required owner-approved release process exception.
Description check	⚠️ Warning	The description includes the release summary, key changes, and testing results, but it omits the required template sections and checklist. It does not explicitly document the release-prep type, local …	Rewrite the description using the repository template. Add the Summary, Changes, Type, Testing, Checklist, and Release cadence sections, select Release prep, and explicitly mark each applicable checklist item, including the regression-fixtu…

✅ Passed checks (7 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (3 skipped: 3 …
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.
Cross-Platform Default Parity	✅ Passed	PASS: The PR changes release metadata, lockfile self-versions, and CHANGELOG.md only. The _FALLBACK_VERSION literal changes from 0.5.5 to 0.5.6, but no platform-dependent default behavior changes. N…
I18n Completeness (21 Locales)	✅ Passed	The PR changes no frontend source files. The only frontend change is the version field in frontend/package.json, so it introduces no new or changed t('...') key and no changed frontend user-facing…
Local-First Guarantee	✅ Passed	PASS — The PR changes only release documentation and version metadata. It adds no runtime network code, account or API-key requirement, or telemetry. The changelog describes integrations but does not …
Backward Compatibility	✅ Passed	No backward-compatibility failure is introduced. The authoritative diff changes only release metadata, lockfile self-versions, and CHANGELOG.md; it changes no voice/project/settings paths, database sc…

Full details: Title check

Explanation

The title identifies a release version bump but does not use the required Conventional Commit format with a scope, and it does not include an issue reference. The repository requirement also states that version bumps must not be proposed.

Full details: Description check

Explanation

The description includes the release summary, key changes, and testing results, but it omits the required template sections and checklist. It does not explicitly document the release-prep type, local testing checklist status, or the required runtime regression-fixture status.

Resolution

Rewrite the description using the repository template. Add the Summary, Changes, Type, Testing, Checklist, and Release cadence sections, select Release prep, and explicitly mark each applicable checklist item, including the regression-fixture status.

• Fix all pre-merge checks with AI

---

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.}