Skip to content

SMOODEV-groq-deprecation: rename removed Groq Llama aliases to gpt-oss#115

Merged
brentrager merged 1 commit into
mainfrom
SMOODEV-groq-deprecation
Jun 29, 2026
Merged

SMOODEV-groq-deprecation: rename removed Groq Llama aliases to gpt-oss#115
brentrager merged 1 commit into
mainfrom
SMOODEV-groq-deprecation

Conversation

@brentrager

Copy link
Copy Markdown
Contributor

Problem

The smooai litellm gateway (PR #2097, merged) deleted the deprecated Groq aliases groq-llama-3.3-70b and groq-llama-3.1-8b. The smooth repo's smooth-judge / smooth-fast semantic slots still routed to those names, so they would return HTTP 400 / 404 once the gateway redeploys.

The rename

  • groq-llama-3.3-70bgroq-gpt-oss-120b (judge / reasoning slot)
  • groq-llama-3.1-8bgroq-gpt-oss-20b (fast slot)

No groq-llama-4*, groq-kimi*, or qwen3-32b references exist anywhere in the repo (verified).

Changes

  • smooth-policy/src/smooth_alias.rs (source of truth): concrete_default() for Judge/Fast → gpt-oss; doc mapping table + tests updated. Added a second migration step migrate_deprecated_concrete(): a config that already ran the smooth-* → concrete migration is pinned to the literal dead Groq name (no smooth- prefix left to re-trigger the slot map), so it would otherwise stay on a dead model. The step rewrites the dead concrete names → gpt-oss. This flows through every consumer (migrate_alias is the shared entry point) — no new mechanism invented.
  • smooth-cast/src/provider_migration.rs: slot/rewrite test expectations updated; new test migrate_bumps_already_migrated_groq_llama_to_gpt_oss proving an already-migrated registry gets bumped + idempotent.
  • smooth-code/src/model_picker.rs: offline catalog entries + fallback/post-migration test expectations renamed.

Historical CHANGELOG.md entries left intact (they describe a past release).

Validation

  • cargo check / cargo fmt --check clean for all three crates.
  • cargo test -p smooai-smooth-policy -p smooai-smooth-cast -p smooai-smooth-code — all green (incl. 2 new tests).
  • Pre-existing unrelated smooth-pearls clippy sort_by_key error is on main too (not touched here).

⚠️ Deploy ordering

Do NOT merge/deploy this before coordinating. smooth deploy must precede the litellm gateway redeploy that removes the old aliases — otherwise in-flight configs still on smooth-judge/smooth-fast briefly map to dead names. Main session reviews + coordinates.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AxL4LdeChNivUCZM6No2NJ

The smooai litellm gateway (PR #2097) deleted the deprecated Groq
aliases `groq-llama-3.3-70b` and `groq-llama-3.1-8b`. The smooth repo's
`smooth-judge` / `smooth-fast` slots routed to those names, so they would
404 once the gateway redeploys.

- smooth-policy/smooth_alias.rs: judge slot -> groq-gpt-oss-120b, fast
  slot -> groq-gpt-oss-20b (concrete_default + doc table + tests). Also
  add a second migration step (migrate_deprecated_concrete) so a config
  ALREADY migrated onto the literal dead Groq names — which carry no
  `smooth-` prefix and so never re-hit the slot mapping — gets bumped to
  the live gpt-oss alias instead of 404ing.
- smooth-cast/provider_migration.rs: update slot/rewrite tests; add a
  test proving an already-migrated registry pinned to groq-llama-3.3-70b
  / groq-llama-3.1-8b is bumped to gpt-oss (and is idempotent).
- smooth-code/model_picker.rs: rename the offline catalog entries and
  fallback/post-migration test expectations.

Historical CHANGELOG.md entries left intact (they describe a past
release). No groq-llama-4 / groq-kimi / qwen3-32b references exist.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AxL4LdeChNivUCZM6No2NJ
@changeset-bot

changeset-bot Bot commented Jun 29, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: dd48850

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@brentrager brentrager merged commit 3010015 into main Jun 29, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant