Skip to content

fix: enhance knowledge base chunk management and unify delete confirmation dialogs #261

fix: enhance knowledge base chunk management and unify delete confirmation dialogs

fix: enhance knowledge base chunk management and unify delete confirmation dialogs #261

Triggered via pull request March 16, 2026 16:49
@Dallas98Dallas98
synchronize #435
fix/rag
Status Success
Total duration 17m 29s
Artifacts
Build and Push Backend Python Docker Image  /  build-and-push-amd
17m 25s
Build and Push Backend Python Docker Image / build-and-push-amd
Build and Push Backend Python Docker Image  /  build-and-push-arm
14m 39s
Build and Push Backend Python Docker Image / build-and-push-arm
Build and Push Backend Python Docker Image  /  manifest
0s
Build and Push Backend Python Docker Image / manifest
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Build and Push Backend Python Docker Image / build-and-push-arm
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 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/
Build and Push Backend Python Docker Image / build-and-push-amd
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 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/