What

• Extend the Anthropic sampling-param deprecation detector in unstract/sdk1/.../adapters/base1.py to cover every Opus release from 4.7 onwards — Opus 4.7, 4.8, 4.9 and Opus 5+ — instead of only claude-opus-4-7.
• Replace the single regex with two anchored patterns:

  _SAMPLING_DEPRECATED_MODEL_PATTERNS = (
      re.compile(r"claude-opus-4-[789](?=$|[-:@/]|v\d)"),  # Opus 4.7, 4.8, 4.9
      re.compile(r"claude-opus-[5-9](?=$|[-:@/]|v\d)"),    # Opus 5 and later
  )

• Trim the oversized leading comment and extend test_sampling_strip.py with 4.8 / 4.9 / Opus 5+ positives and Opus 5 boundary negatives.

Why

PR #1934 added the strip but keyed it to a single literal — claude-opus-4-7. Anthropic has since shipped Opus 4.8, which deprecates the same sampling parameters (temperature, top_p, top_k). Because claude-opus-4-8 does not match the old pattern, those calls reach the provider with temperature still set and 400:

{"type":"error","error":{"type":"invalid_request_error",
"message":"`temperature` is deprecated for this model."}}

litellm cannot fix this for us — upstream get_supported_openai_params() still reports temperature as supported for these models (open bug BerriAI/litellm#26444, unshipped), so drop_params=True is a no-op. The strip in base1.py remains the only thing preventing the 400, and it must track each new Opus id.

Reference: https://platform.claude.com/docs/en/about-claude/models/whats-new-claude-4-7

How

base1.py:

• The lone claude-opus-4-7 pattern becomes two patterns covering claude-opus-4-[789] and claude-opus-[5-9]. The existing trailing-edge lookahead ($, a -/:/@// delimiter, or v<digit>) is preserved, so:
  • Match: every encoding of 4.7/4.8/4.9 and Opus 5+ — native (claude-opus-4-8), Bedrock foundation models / cross-region profiles / ARNs (us.anthropic.claude-opus-4-8-<date>-v1:0), Vertex (vertex_ai/claude-opus-4-8@<date>), Azure deployments embedding the id, and dot/underscore variants.
  • Do not match: prefix collisions (claude-opus-4-70, claude-opus-4-7verbose), the sampling-supporting claude-opus-4-1..4-6, and Opus 5 boundary cases (claude-opus-50, claude-opus-5verbose).
• No change to _strip_deprecated_sampling_params, the model/model_id AIP fallback, or the four adapter call sites — only the detection table widened.

test_sampling_strip.py:

• New positives for 4.8 (representative encodings: native, anthropic/, Bedrock id + ARN, cross-region, Vertex, Azure, dotted), 4.9, and Opus 5/6.
• New negatives locking the new boundaries: claude-opus-50, claude-opus-5verbose, claude-opus-4-1, anthropic.claude-opus-4-1-....
• All 78 tests pass.

Known limitation

claude-opus-4-[789] covers 4.7–4.9 but not a hypothetical claude-opus-4-10. Anthropic's cadence (4-5 → 4-6 → 4-7 → 4-8) makes an Opus 5 jump far more likely than a 4-10, and Opus 5+ is already covered. Fable 5 / Mythos 5 (claude-fable-5, claude-mythos-5) also forbid these params but are out of scope here (this change is Opus-only, per the "4.7 onwards" scope); they would each need a pattern if routed through this SDK.

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

No.

• The change only widens which model ids trigger the strip; it adds no new behavior for models already handled.
• Models that retain temperature / top_p / top_k are unaffected — verified by negative tests for claude-opus-4-1..4-6, claude-sonnet-4-7, claude-haiku-4-5, claude-3-5-sonnet, and non-Anthropic providers (gpt-4o, gemini-2.0-flash), which all keep their sampling params.
• The trailing-edge anchor is unchanged, so prior false-match guards (claude-opus-4-70, claude-opus-4-7verbose) still hold.
• The _strip_deprecated_sampling_params contract, AIP model_id fallback, and adapter wiring are untouched.

🤖 Generated with Claude Code