Skip to content

Rename reject approval policy to granular (#14516) #15303

Rename reject approval policy to granular (#14516)

Rename reject approval policy to granular (#14516) #15303

Triggered via push March 12, 2026 23:38
Status Failure
Total duration 16m 11s
Artifacts

bazel.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 8 warnings
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Process completed with exit code 3.
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Process completed with exit code 3.
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@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/
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Failed to restore: Cache service responded with 400
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@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/
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Failed to restore: Cache service responded with 400
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@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/
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Failed to restore: Cache service responded with 400
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@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/
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Failed to restore: Cache service responded with 400