Skip to content

feat: Support configOverrides for config.json #138

feat: Support configOverrides for config.json

feat: Support configOverrides for config.json #138

Triggered via pull request April 8, 2026 11:09
Status Failure
Total duration 5m 41s
Artifacts 1

build.yaml

on: pull_request
Detect relevant changed files
5s
Detect relevant changed files
Matrix: build-container-image
Run cargo-udeps
2m 21s
Run cargo-udeps
Package/Publish ${{ needs.build-container-image.outputs.operator-version }} Helm Chart
0s
Package/Publish ${{ needs.build-container-image.outputs.operator-version }} Helm Chart
Publish/Sign ${{ needs.build-container-image.outputs.operator-version }} Index
0s
Publish/Sign ${{ needs.build-container-image.outputs.operator-version }} Index
Matrix: openshift-preflight-check
Failure Notification
7s
Failure Notification
Finished Build and Publish
0s
Finished Build and Publish
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
Run cargo-udeps
Process completed with exit code 101.
Build/Publish arm64 Image
Process completed with exit code 1.
Build/Publish amd64 Image
Process completed with exit code 1.
Failure Notification
Unable to download artifact(s): Artifact not found for name: slack-thread-id-24132268205 Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Run cargo-udeps
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, Swatinem/rust-cache@98c8021b550208e191a6a3145459bfc9fb29c4c0. 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/
Build/Publish arm64 Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Build/Publish amd64 Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f. 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/
Failure Notification
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a. 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
slack-thread-id-24132268205
164 Bytes
sha256:d82fcb66d7aa1d97a82bbc1bcbad7898cf44ed93a771541d89b38c010f746e46