chore(frontend): React 18.3 deprecation checkpoint (#12899) (#13080) #3349
google-oss-prow[bot]legacy-v2-api-integration-tests.yml
on: push
Matrix: build / image-build
Matrix: api-integration-tests-v2
Annotations
7 errors and 15 warnings
|
API integration tests v2 - K8s with kubernetes v1.34.0 pod_to_pod_tls_enabled=false
Canceling since a higher priority waiting request for legacy-integration-v2-tests-refs/heads/master exists
|
|
API integration tests v2 - K8s with kubernetes v1.34.0 pod_to_pod_tls_enabled=false
The operation was canceled.
|
|
API integration tests v2 - K8s with database v1.34.0 pod_to_pod_tls_enabled=false
Canceling since a higher priority waiting request for legacy-integration-v2-tests-refs/heads/master exists
|
|
API integration tests v2 - K8s with database v1.34.0 pod_to_pod_tls_enabled=false
The operation was canceled.
|
|
API integration tests v2 - K8s with database v1.34.0 pod_to_pod_tls_enabled=true
Canceling since a higher priority waiting request for legacy-integration-v2-tests-refs/heads/master exists
|
|
API integration tests v2 - K8s with database v1.34.0 pod_to_pod_tls_enabled=true
The operation was canceled.
|
|
KFP API Integration V2 (Legacy)
Canceling since a higher priority waiting request for legacy-integration-v2-tests-refs/heads/master exists
|
|
build / image-build (metadata-envoy, third_party/metadata_envoy/Dockerfile, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (metadata-writer, backend/metadata_writer/Dockerfile, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (cache-deployer, backend/src/cache/deployer/Dockerfile, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (viewer-crd-controller, backend/Dockerfile.viewercontroller, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (scheduledworkflow, backend/Dockerfile.scheduledworkflow, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (persistenceagent, backend/Dockerfile.persistenceagent, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (frontend, frontend/Dockerfile, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (launcher, backend/Dockerfile.launcher, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (driver, backend/Dockerfile.driver, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (cache-server, backend/Dockerfile.cacheserver, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (visualization-server, backend/Dockerfile.visualization, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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 / image-build (apiserver, backend/Dockerfile, .)
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, docker/build-push-action@v5, docker/setup-buildx-action@v3. 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/
|
|
API integration tests v2 - K8s with kubernetes v1.34.0 pod_to_pod_tls_enabled=false
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
API integration tests v2 - K8s with database v1.34.0 pod_to_pod_tls_enabled=false
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
|
API integration tests v2 - K8s with database v1.34.0 pod_to_pod_tls_enabled=true
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/upload-artifact@v4, nick-fields/retry@ce71cc2ab81d554ebbe88c79ab5975992d79ba08. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
apiserver
Expired
|
86.5 MB |
sha256:6c6bc64a15b1b0c613dee5896af727060d81431cccf959f91c9e8016bd22e9c1
|
|
|
cache-deployer
Expired
|
284 MB |
sha256:9cdd137ae56b1772214bb6de233cde3b8904442a252bd1a0921475597e18bfc7
|
|
|
cache-server
Expired
|
34.1 MB |
sha256:5d51f1e3352e731b786db41aff5582a225d43b53aad7448f27d9a56f3430fac0
|
|
|
driver
Expired
|
51.8 MB |
sha256:7258dc196415f5f295afd576ec290b63779d1bf696dd291128bd35f5a8c65e7c
|
|
|
frontend
Expired
|
166 MB |
sha256:8307423da40bd5ad395221e53779b2938e9f11af99976c895b7f934a1b197f24
|
|
|
kfp-api-integration-tests-v2-artifacts-k8s-v1.34.0-database-tls-false
|
20.5 KB |
sha256:3cf7dba32641a213241946a8a0f1409f1de621ecf7de15da0d95b3cad8548f58
|
|
|
kfp-api-integration-tests-v2-artifacts-k8s-v1.34.0-database-tls-true
|
20.7 KB |
sha256:a5da35868621cda2d7236c811c94650258ce5babfd1a36068e2e5c7754648524
|
|
|
kfp-api-integration-tests-v2-artifacts-k8s-v1.34.0-kubernetes-tls-false
|
21.1 KB |
sha256:ac12e2e8f5384845e38bc671901009697a635c7eb32b8cc3c4caf2a7aa281f62
|
|
|
launcher
Expired
|
49.6 MB |
sha256:2b03e0cfe6a932620a3559bda995ca2f3cb9db1c666f186ec209cc59aa2c934e
|
|
|
metadata-envoy
Expired
|
126 MB |
sha256:16f20859efccacb15238f949c7083b1c7a79011e2cd7c53131ee189a6cc6f182
|
|
|
metadata-writer
Expired
|
87 MB |
sha256:4f4df9f43b3c832dfd59ae919b6c445cdd34c2bae03c81970a2a53cf2160dc26
|
|
|
persistenceagent
Expired
|
31.7 MB |
sha256:95cfd4f730244fbec2e4eb76151139047c3d246ee701e694e1fcdf3d4d5eebd6
|
|
|
scheduledworkflow
Expired
|
36.3 MB |
sha256:c0a8dadd95d4318951e24ab94c0bdc9ab6b4b2b897413e98d00f71a013f22fef
|
|
|
viewer-crd-controller
Expired
|
27.6 MB |
sha256:dff6f8bc16dff56cb76836999152c7211d16f765cf64a3b9c416ee89ae013615
|
|
|
visualization-server
Expired
|
952 MB |
sha256:1c1a0fe7444a6e3479380f0871c356ebdef2b8f8f3d0aebefee268a54f835b7e
|
|