chore: update TTS Audio

[fishaudio-bot]

Auto-generated TTS audio for updated documentation

Summary by CodeRabbit

• Documentation
  • Updated model availability information with Fish Audio S1 listed as the recommended option for new projects
  • Marked speech-1.6 and speech-1.5 as deprecated effective February 28, 2026
  • Enhanced support resources

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the deprecations documentation to introduce an "Available Models" section listing Fish Audio S1 as the current recommended model and marking speech-1.6 and speech-1.5 as deprecated effective February 28, 2026, with guidance for new projects.

Changes

Cohort / File(s)	Summary
Documentation Update developer-guide/models-pricing/deprecations.mdx	Added "Available Models" section with Fish Audio S1 as recommended current model; introduced "Deprecated Models" list for speech-1.6 and speech-1.5 with February 28, 2026 deprecation date; updated metadata hash and formatting.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• deprecation notice #43: Makes identical content-level changes to the deprecations.mdx file by adding the "Available Models" section with Fish Audio S1 and deprecated model listings.
• chore: update TTS Audio #44: Modifies the same deprecations.mdx file with speak-mintlify-hash updates and formatting adjustments.

Suggested reviewers

• twangodev

Poem

🐰 With S1 now shining bright and clear,
Old speech models fade from here,
February marks their final day,
New projects find a better way! 🎯

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: update TTS Audio' is vague and does not clearly specify what is being updated. While it mentions TTS Audio, it lacks detail about the actual changes such as model deprecations or the introduction of new Fish Audio S1 model.	Consider a more descriptive title like 'chore: deprecate legacy TTS models and recommend Fish Audio S1' to better reflect the substantive documentation updates.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/tts-updates

---

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

developer-guide/models-pricing/deprecations.mdx (1)

52-53: ⚠️ Potential issue | 🟡 Minor

Fix date formatting: remove stray comma and ordinal suffix.

"February, 28th, 2026" should be "February 28, 2026" — the comma after the month is incorrect, and ordinal suffixes are unconventional in technical docs.

Proposed fix

-- **speech-1.6** - Fish Speech v1.6 will be deprecated on February, 28th, 2026
-- **speech-1.5** - Fish Speech v1.5 will be deprecated on February, 28th, 2026
+- **speech-1.6** - Fish Speech v1.6 will be deprecated on February 28, 2026
+- **speech-1.5** - Fish Speech v1.5 will be deprecated on February 28, 2026

🧹 Nitpick comments (1)

developer-guide/models-pricing/deprecations.mdx (1)

55-57: Use second-person voice per guidelines.

"We strongly recommend" should be rephrased to address the reader directly.

Proposed fix

 <Note>
-We strongly recommend using **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements.
+You should use **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements.
 </Note>

As per coding guidelines, "Use second-person voice ('you') in documentation content".