feat(gateway): support profile and routing_group

[Kludex]

Note

Adds optional routing_group and profile params to gateway_provider that set corresponding Gateway headers; includes tests.

• Gateway Provider (pydantic_ai/providers/gateway.py)
  • Add optional routing_group and profile parameters across overloads and implementation.
  • Set HTTP headers pydantic-ai-gateway-routing-group and pydantic-ai-gateway-profile when provided.
  • Update docstring to document new params and behavior.
• Tests (tests/providers/test_gateway.py)
  • Add tests validating headers for routing_group and profile.
  • Keep existing provider initialization and routing behavior unchanged.

^{Written by Cursor Bugbot for commit 5a757e2. This will update automatically on new commits. Configure here.}

[github-actions]

Docs Preview

commit:	5a757e2
Preview URL:	https://5a16fac7-pydantic-ai-previews.pydantic.workers.dev

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on December 9

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Cached Client Headers: Stale Values Persist

Using setdefault to add profile and routing_group headers causes incorrect behavior when the cached HTTP client is reused. Since cached_async_http_client returns the same client instance for the same api_type, subsequent calls with different profile or routing_group values won't update the headers because setdefault only sets values for keys that don't exist. This means the second call will incorrectly use headers from the first call instead of the newly specified values.

 

[Kludex]

Fair.