Skip to content

Fix renamed interlocks #7274

Fix renamed interlocks

Fix renamed interlocks #7274

Triggered via pull request May 11, 2026 15:39
Status Failure
Total duration 9m 36s
Artifacts 2

ci.yml

on: pull_request
Matrix: test
pypi  /  upload
pypi / upload
release  /  artifacts
release / artifacts
helm  /  build
helm / build
debug_container  /  build
debug_container / build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 4 warnings
require-label / label
Please add a label to this PR. This helps with generating helpful release notes.
test (ubuntu-latest, 3.11) / run
Process completed with exit code 2.
test (ubuntu-latest, 3.12) / run
Process completed with exit code 2.
test (ubuntu-latest, 3.13) / run
Process completed with exit code 2.
lint / run
Process completed with exit code 1.
docs / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
dist / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
dist / build
Failed to save: Unable to reserve cache with key setup-uv-2-x86_64-unknown-linux-gnu-ubuntu-24.04-3.12.3-pruned-22a277699e51c2c79256a640c4d6b807d2dfe4024eef93ac2a43ef2d5fd5f763, another job may be creating this cache.
container / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-action@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
dist
3.91 MB
sha256:cf49b622cf4ec24d2f7816d550bac6a90a69cbc6cc928edb449f8eb095836a38
docs
3.21 MB
sha256:30166176bff7df841fef01a9e9e6bfcd0952a163962aff43fcb4f2de69d7f534