Skip to content

update bazel version to 2.3.0 too #894

update bazel version to 2.3.0 too

update bazel version to 2.3.0 too #894

Triggered via push July 3, 2026 14:20
Status Success
Total duration 2m 51s
Artifacts

bazel_build.yml

on: push
Matrix: bazel-build-check
Fit to window
Zoom out
Zoom in

Annotations

14 warnings and 1 notice
bazel-build-check (ubuntu-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, bazel-contrib/setup-bazel@0.9.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
bazel-build-check (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oMVHagAAAABa2AnEH52XT4L9lFo2y1hjQ0hJMzBFREdFMDQwOABFZGdl
bazel-build-check (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0n8VHagAAAACLgUQSpNOUT6XRE11Sce26Q0hJMzBFREdFMDQwOABFZGdl
bazel-build-check (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0n8VHagAAAAC/cq8aggJ4T4Wo7LeCeUPzQ0hJMzBFREdFMDQwOABFZGdl
bazel-build-check (ubuntu-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (ubuntu-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (ubuntu-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, bazel-contrib/setup-bazel@0.9.0. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
bazel-build-check (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>03cVHagAAAABmxt12GFoFRJu1P75p9ve9TEFYMzExMDAwMTE0MDI5AEVkZ2U=
bazel-build-check (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>028VHagAAAACxOVrU47u/S6AHEsantJ/nTEFYMzExMDAwMTE0MDI5AEVkZ2U=
bazel-build-check (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>02sVHagAAAADoM94OZHudSqCcNoB6C4JiTEFYMzExMDAwMTE0MDI5AEVkZ2U=
bazel-build-check (macos-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
The macos-latest label will migrate to macOS 26 beginning June 15, 2026. For more information see https://github.com/actions/runner-images/issues/14167