Skip to content

Merge remote-tracking branch 'origin/Feature/BackFiller' into Feature… #727

Merge remote-tracking branch 'origin/Feature/BackFiller' into Feature…

Merge remote-tracking branch 'origin/Feature/BackFiller' into Feature… #727

Triggered via push June 1, 2026 12:37
Status Cancelled
Total duration 1m 0s
Artifacts

ci.yml

on: push
build-docker  /  build-push
54s
build-docker / build-push
lint-and-test  /  tests
lint-and-test / tests
tag-deploy-fast  /  build-push
tag-deploy-fast / build-push
tag-deploy  /  build-push
tag-deploy / build-push
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
build-docker / build-push
Canceling since a higher priority waiting request for refs/heads/Feature/BackFiller exists
build-docker / build-push
The operation was canceled.
Build image and push to registry
Canceling since a higher priority waiting request for refs/heads/Feature/BackFiller exists
Build image and push to registry
Canceling since a higher priority waiting request for refs/heads/Feature/BackFiller exists
build-docker / build-push
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v6, docker/login-action@v3, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/