Update google provider types - #402
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 63164e1d30
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "Codex (@codex) address that feedback".
| bedrock: null, | ||
| }, | ||
|
|
||
| googleAudioTranscriptionConfigParam: (() => { |
There was a problem hiding this comment.
Add transform captures for the new Google case
When CI runs payload tests, payloads/scripts/sync.test.ts enumerates every case with a Google source and requires transform captures for google_to_anthropic, google_to_chat-completions, and google_to_responses. This new Google case only adds provider snapshots, so payloads/transforms/google_to_{anthropic,chat-completions,responses}/googleAudioTranscriptionConfigParam.json are missing and the sync check fails; capture the transform fixtures for this case before landing.
AGENTS.md reference: AGENTS.md:L138-L141
Useful? React with 👍 / 👎.
Automated update of Lingua provider types.
Provider:
googleFeedback: comment
/bt goodor/bt badto log review feedback to the Braintrust trace.Validation
./pipelines/generate-provider-types.sh google: successmake generate-types: successmake generate-types: successcargo fmt --all: successcargo test -p lingua google: successmake lingua-wasm: successgoogleAudioTranscriptionConfigParammake test-payloads: successcargo build --all-features: successcargo clippy --all-targets --all-features -- -D warnings: successmake typed-boundary-check: successcargo test -p coverage-report --test cross_provider_test cross_provider_transformations_have_no_unexpected_failures: successThis PR is created even when validation fails so the generated update and repair attempt are available for manual follow-up.