docs: remove latency_optimized restrictions and add release note#372
Merged
jason-gardella-deepl merged 5 commits intoJun 17, 2026
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
latency_optimized is now fully compatible with all Translate API features including tag handling v2, style rules, custom instructions, translation memories, and all language pairs. Removes outdated warnings, error descriptions, and compatibility tables that stated these combinations would be rejected. Adds a June 15 release note announcing the change. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Remove redundant Info box about THv2 compatibility (per review feedback) - Update release note date from June 15 to June 17 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jason-gardella-deepl
force-pushed
the
fix/remove-latency-optimized-restrictions
branch
from
0340822 to
309f7b0
Compare
The API now always respects the requested model_type. Removed statements saying features default to quality_optimized when no model_type is specified. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
shirgoldbird
approved these changes
Jun 17, 2026
jason-gardella-deepl
deleted the
fix/remove-latency-optimized-restrictions
branch
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
2 participants
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.
Summary
Removes all documentation stating that
model_type=latency_optimizedis incompatible with certain features.latency_optimizedis now fully supported with all Translate APIfeatures.
Changes across 8 files
Restrictions removed:
style_id): Was "will be rejected" → now supportedFiles changed:
api-reference/translate.mdx— Updated parameter descriptions for style_id, custom_instructions, translation_memory_id, and tag_handling_versionapi-reference/style-rules.mdx— Updated style_id info boxapi-reference/openapi.json— Updated schema descriptionsapi-reference/openapi.yaml— Updated schema descriptionsdocs/xml-and-html-handling/tag-handling-v2.mdx— Updated compatibility table and removed warningdocs/best-practices/custom-instructions.mdx— Removed error warningdocs/learning-how-tos/examples-and-guides/translation-beginners-guide.mdx— Updated special casesdocs/resources/roadmap-and-release-notes.mdx— Added June 15 release note + updated Jan 8 noteRelease note added:
June 15 entry announcing
latency_optimizedis now supported for all features, listing the specific features that were previously restricted.Context
This is the documentation counterpart to the Dynamic Workflows migration work. The DW workflow code now handles
latency_optimizedwith all features via thesplit_mode_follows_requested_model_typeflag (dynamic-workflows!2111 and follow-ups).🤖 Generated with Claude Code