Skip to content

fix: Robust multipart content handling in Gemini CLI provider #711

fix: Robust multipart content handling in Gemini CLI provider

fix: Robust multipart content handling in Gemini CLI provider #711

Triggered via issue March 16, 2026 21:30
@DaycloneDayclone
commented on #150 bf7ab7e
Status Success
Total duration 2m 45s
Artifacts –

bot-reply.yml

on: issue_comment
continuous-reply
2m 40s
continuous-reply
Fit to window
Zoom out
Zoom in

Annotations

3 warnings and 1 notice
continuous-reply
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/create-github-app-token@v1, astral-sh/setup-uv@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
continuous-reply
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>0GXe4aQAAAAC9ExzG8gffSp7eilol0A7xUEhMMzBFREdFMDEwNgBFZGdl
continuous-reply
Failed to restore: Cache service responded with 400
continuous-reply
Valid trigger found in non-quoted, non-code text.