Open
Conversation
📝 WalkthroughWalkthroughThis PR updates documentation metadata and content: it adds an "Available Models" section recommending Fish Audio S1, marks speech-1.6 and speech-1.5 as deprecated (deprecation date Feb 28, 2026), and adjusts several internal minified-hash comments and minor formatting/spacing in speech-to-text docs. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 | 🟡 MinorFix grammatical error in date format.
The dates have an incorrect comma after the month name. "February, 28th, 2026" should be "February 28th, 2026" or "February 28, 2026".
📝 Proposed fix
## Deprecated Models -- **speech-1.6** - Fish Speech v1.6 has been deprecated on February, 28th, 2026 -- **speech-1.5** - Fish Speech v1.5 has been deprecated on February, 28th, 2026 +- **speech-1.6** - Fish Speech v1.6 has been deprecated on February 28th, 2026 +- **speech-1.5** - Fish Speech v1.5 has been deprecated on February 28th, 2026🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@developer-guide/models-pricing/deprecations.mdx` around lines 52 - 53, Update the two deprecation lines for **speech-1.6** and **speech-1.5** to remove the erroneous comma after the month—replace "February, 28th, 2026" with a correct date format such as "February 28th, 2026" (or "February 28, 2026") so both entries read "Fish Speech v1.6 has been deprecated on February 28th, 2026" and "Fish Speech v1.5 has been deprecated on February 28th, 2026".
🧹 Nitpick comments (1)
developer-guide/models-pricing/deprecations.mdx (1)
55-57: Consider using second-person voice for consistency.The guideline specifies using second-person voice ("you") in documentation content. The current phrasing "We strongly recommend using" uses first-person plural.
📝 Suggested rephrasing
<Note> -We strongly recommend using **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements. +For all new projects, you should use **Fish Audio S1** to access the latest capabilities and performance improvements. </Note>As per coding guidelines: "Use second-person voice ("you") in documentation content".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@developer-guide/models-pricing/deprecations.mdx` around lines 55 - 57, Update the Note block that currently reads "We strongly recommend using **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements." to second-person voice by replacing "We strongly recommend using" with phrasing like "You should use" or "You should strongly consider using" (e.g., "You should strongly consider using **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements.") so the sentence uses "you" and matches the documentation voice; keep the Note tag and the product name "**Fish Audio S1**" unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@developer-guide/models-pricing/deprecations.mdx`:
- Around line 52-53: Update the two deprecation lines for **speech-1.6** and
**speech-1.5** to remove the erroneous comma after the month—replace "February,
28th, 2026" with a correct date format such as "February 28th, 2026" (or
"February 28, 2026") so both entries read "Fish Speech v1.6 has been deprecated
on February 28th, 2026" and "Fish Speech v1.5 has been deprecated on February
28th, 2026".
---
Nitpick comments:
In `@developer-guide/models-pricing/deprecations.mdx`:
- Around line 55-57: Update the Note block that currently reads "We strongly
recommend using **Fish Audio S1** for all new projects to access the latest
capabilities and performance improvements." to second-person voice by replacing
"We strongly recommend using" with phrasing like "You should use" or "You should
strongly consider using" (e.g., "You should strongly consider using **Fish Audio
S1** for all new projects to access the latest capabilities and performance
improvements.") so the sentence uses "you" and matches the documentation voice;
keep the Note tag and the product name "**Fish Audio S1**" unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 4813bb6a-f6bd-421e-9c6a-a8afc518c803
📒 Files selected for processing (1)
developer-guide/models-pricing/deprecations.mdx
fishaudio-bot
force-pushed
the
chore/tts-updates
branch
from
8286227 to
05094e2
Compare
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
developer-guide/models-pricing/deprecations.mdx (2)
52-53:⚠️ Potential issue | 🟡 MinorNormalize the deprecation date wording.
on February, 28th, 2026reads awkwardly in docs. Use a standard form likeon February 28, 2026oras of February 28, 2026for both bullets.Suggested edit
-- **speech-1.6** - Fish Speech v1.6 has been deprecated on February, 28th, 2026 -- **speech-1.5** - Fish Speech v1.5 has been deprecated on February, 28th, 2026 +- **speech-1.6** - Fish Speech v1.6 was deprecated on February 28, 2026 +- **speech-1.5** - Fish Speech v1.5 was deprecated on February 28, 2026As per coding guidelines, "Prioritize accuracy and usability of information" and "Match style and formatting of existing pages".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@developer-guide/models-pricing/deprecations.mdx` around lines 52 - 53, Update the two deprecation bullets for **speech-1.6** and **speech-1.5** to normalize the date wording to match the docs style; replace "on February, 28th, 2026" with a standard form such as "on February 28, 2026" (or "as of February 28, 2026") so both lines read consistently and correctly.
55-56:⚠️ Potential issue | 🟡 MinorUse second-person voice in the note.
We strongly recommend...breaks the docs style rule here. Rewrite it as direct guidance to the reader.Suggested edit
<Note> -We strongly recommend using **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements. +For new projects, you should use **Fish Audio S1** to access the latest capabilities and performance improvements. </Note>As per coding guidelines, "Use second-person voice ("you") in documentation content".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@developer-guide/models-pricing/deprecations.mdx` around lines 55 - 56, The note currently uses third-person phrasing ("We strongly recommend using **Fish Audio S1** for all new projects…"); change it to second-person imperative guidance by rewriting the sentence in the Note block to address the reader directly (for example: "Use **Fish Audio S1** for all new projects to access the latest capabilities and performance improvements."). Update the Note content so it uses "you"/imperative voice and maintains the bold product name and explanation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@developer-guide/models-pricing/deprecations.mdx`:
- Around line 52-53: Update the two deprecation bullets for **speech-1.6** and
**speech-1.5** to normalize the date wording to match the docs style; replace
"on February, 28th, 2026" with a standard form such as "on February 28, 2026"
(or "as of February 28, 2026") so both lines read consistently and correctly.
- Around line 55-56: The note currently uses third-person phrasing ("We strongly
recommend using **Fish Audio S1** for all new projects…"); change it to
second-person imperative guidance by rewriting the sentence in the Note block to
address the reader directly (for example: "Use **Fish Audio S1** for all new
projects to access the latest capabilities and performance improvements.").
Update the Note content so it uses "you"/imperative voice and maintains the bold
product name and explanation.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3f811a98-1f24-4482-9833-d260fa254d15
📒 Files selected for processing (3)
developer-guide/core-features/speech-to-text.mdxdeveloper-guide/models-pricing/deprecations.mdxdeveloper-guide/sdk-guide/javascript/speech-to-text.mdx
✅ Files skipped from review due to trivial changes (2)
- developer-guide/core-features/speech-to-text.mdx
- developer-guide/sdk-guide/javascript/speech-to-text.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-generated TTS audio for updated documentation
Summary by CodeRabbit
Release Notes