Skip to content

fix(amazon-bedrock): correct Meta, Mistral, and Writer catalog - #6791

Merged
rekram1-node merged 3 commits into
devfrom
feat/bedrock-mistral
Sep 12, 2026
Merged

fix(amazon-bedrock): correct Meta, Mistral, and Writer catalog#6791
rekram1-node merged 3 commits into
devfrom
feat/bedrock-mistral

Conversation

@rekram1-node

Copy link
Copy Markdown
Collaborator

Summary

Meta/Mistral/Writer split of #6637, based on current dev.

  • Audit all 25 existing entries; preserve every existing ID and route.
  • Add complete shared lab metadata for Magistral, Ministral 3, and Voxtral models.
  • Correct Writer X4/X5 native metadata while keeping Bedrock host limits as provider overrides.
  • Correct Llama 3.3/4 and Mistral dates, modalities, capabilities, and confirmed host limits.
  • Correct Voxtral Small pricing.

Live checks confirmed Llama 4’s 8,192 output limit, Bedrock Scout’s AWS-documented 10M context, and Ministral 8B/14B image input. Proposed Llama 3.2 additions were excluded after AWS returned explicit end-of-life errors.

Sources are in leading TOML comments, including AWS cards and first-party model configs.

Validation

  • bun validate
  • All new lab entries contain required capabilities, modalities, context, and output
  • git diff --check
  • No model deletions or route changes

@github-actions

Copy link
Copy Markdown
Contributor

Action items

  • [high] [possible mistake] providers/amazon-bedrock/models/writer.palmyra-x4-v1:0.toml:11 - Check: Bedrock host limits must remain real overrides of the shared lab window (limit.context / limit.output), not a renamed field. Why: Lab writer/palmyra-x4 now uses context = 128_000. The Bedrock files replace the previous host context = 122_880 with input = 122_880 only, so deep-merge publishes limit.context = 128_000 for writer.palmyra-x4-v1:0 and us.writer.palmyra-x4-v1:0 instead of the prior Bedrock window. That contradicts the PR goal of keeping Bedrock host limits and diverges from the X5 pattern, which still overrides context. Action: If Bedrock’s window is still 122,880, set [limit] context = 122_880 (and output = 8_192) on both X4 routes; use limit.input only if AWS documents a distinct max-input cap in addition to context. Align us.writer.palmyra-x4-v1:0.toml the same way.

@rekram1-node

Copy link
Copy Markdown
Collaborator Author

Fixed in f91f6c1. Both Palmyra X4 provider entries now preserve Bedrock’s limit.context = 122_880 and limit.output = 8_192; the erroneous limit.input replacement is removed. bun validate and git diff --check pass.

@github-actions

Copy link
Copy Markdown
Contributor

No actionable findings.

@github-actions github-actions Bot added the reviewer: ready Automated review found no actionable items label Sep 11, 2026
@github-actions github-actions Bot removed the reviewer: ready Automated review found no actionable items label Sep 11, 2026
@rekram1-node

Copy link
Copy Markdown
Collaborator Author

Follow-up from metadata review: Palmyra X4 keeps the corrected release_date = 2024-10-09, but last_updated is restored to its existing later value 2025-04-28. Release and last update are distinct facts. bun validate passes.

@github-actions

Copy link
Copy Markdown
Contributor

No actionable findings.

@github-actions github-actions Bot added the reviewer: ready Automated review found no actionable items label Sep 11, 2026
@rekram1-node
rekram1-node merged commit 4d24799 into dev Sep 12, 2026
2 checks passed
@rekram1-node
rekram1-node deleted the feat/bedrock-mistral branch September 12, 2026 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

reviewer: ready Automated review found no actionable items

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant