Skip to content

fix: resolve 400 API errors for Gemini, Mistral, and other OpenAI-compatible providers #933

fix: resolve 400 API errors for Gemini, Mistral, and other OpenAI-compatible providers

fix: resolve 400 API errors for Gemini, Mistral, and other OpenAI-compatible providers #933

Triggered via pull request April 11, 2026 15:53
Status Success
Total duration 28s
Artifacts

pr-checks.yml

on: pull_request
smoke-and-tests
24s
smoke-and-tests
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
smoke-and-tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@0a5c61591373683505ea898e09a3ea4f39ef2b9c, oven-sh/setup-bun@4bc047ad259df6fc24a6c9b0f9a0cb08cf17fbe5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
smoke-and-tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mG7aaQAAAABvIdPmkJUMRJtT0dPJCmXxUEhMMzBFREdFMDExMgBFZGdl
smoke-and-tests
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mG7aaQAAAABbHFRjXLVeTpXBF06x+VnaUEhMMzBFREdFMDIxNwBFZGdl
smoke-and-tests
Failed to restore: Cache service responded with 400
smoke-and-tests
Failed to restore: Cache service responded with 400