fix(providers): add ProviderType.GEMINI to FALLBACK_ORDER #11064

Merged
HAL9000 merged 3 commits from fix/gemini-fallback-order-fix-3 into master 2026-06-15 02:43:56 +00:00

3 Commits

Author SHA1 Message Date
controller-ci-rerun 6a5c5c4a42 chore: re-trigger CI [controller]
CI / build (pull_request) Successful in 47s
CI / lint (pull_request) Successful in 49s
CI / helm (pull_request) Successful in 1m4s
CI / typecheck (pull_request) Successful in 1m7s
CI / quality (pull_request) Successful in 1m7s
CI / security (pull_request) Successful in 1m13s
CI / push-validation (pull_request) Successful in 24s
CI / unit_tests (pull_request) Successful in 5m58s
CI / docker (pull_request) Successful in 1m45s
CI / integration_tests (pull_request) Successful in 8m27s
CI / coverage (pull_request) Successful in 11m25s
CI / status-check (pull_request) Successful in 2s
2026-06-14 21:28:31 -04:00
HAL9000 579a99d8b6 docs: update CHANGELOG and CONTRIBUTORS for ProviderType.GEMINI fix
Updated CHANGELOG.md with entry under [Unreleased] > Fixed section,
and ensured CONTRIBUTORS.md includes the bot contributor.

ISSUES CLOSED: #10906
2026-06-14 21:28:31 -04:00
HAL9000 0fd503226b fix(providers): add ProviderType.GEMINI to FALLBACK_ORDER
Add ProviderType.GEMINI to both ProviderRegistry.FALL_BACK_ORDER and
FallbackSelector.DEFAULT_FALLBACK_ORDER, ensuring Gemini is included
in provider fallback chains for auto-discovery. Also remove the
@tdd_expected_fail tag from the TDD regression test since the bug
is now fixed.

ISSUES CLOSED: #10906
2026-06-14 21:28:31 -04:00