Files
cleveragents-core/features
HAL9000 be4dee2a5f
CI / benchmark-publish (pull_request) Has been skipped
CI / helm (pull_request) Successful in 32s
CI / build (pull_request) Successful in 53s
CI / lint (pull_request) Successful in 56s
CI / quality (pull_request) Successful in 1m15s
CI / typecheck (pull_request) Successful in 1m31s
CI / security (pull_request) Successful in 1m34s
CI / push-validation (pull_request) Successful in 21s
CI / integration_tests (pull_request) Successful in 3m30s
CI / e2e_tests (pull_request) Successful in 3m54s
CI / unit_tests (pull_request) Failing after 4m42s
CI / docker (pull_request) Has been skipped
CI / coverage (pull_request) Successful in 11m25s
CI / status-check (pull_request) Failing after 3s
fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER
ProviderType.GEMINI was missing from FALLBACK_ORDER, causing users who
configure only GEMINI_API_KEY (without GOOGLE_API_KEY) to never have
Gemini auto-selected as the default provider. get_default_provider_type()
would return None instead of ProviderType.GEMINI for Gemini-only setups.

Fix: add ProviderType.GEMINI to FALLBACK_ORDER after ProviderType.GOOGLE,
since GEMINI and GOOGLE share the same underlying model family but use
different API keys (GEMINI_API_KEY vs GOOGLE_API_KEY).

Also adds:
- TDD regression test (tdd_gemini_fallback_order_4750.feature) with
  @tdd_issue @tdd_issue_4750 tags (without @tdd_expected_fail since fix applied)
- New BDD scenarios in provider_registry_coverage.feature verifying GEMINI
  is in FALLBACK_ORDER and that Gemini-only users get GEMINI as default
- New step definitions for GEMINI fallback order verification

ISSUES CLOSED: #4750
2026-04-28 09:37:24 +00:00
..