Skip to content

fix(deps): disable bazelisk cache to fix stale Bazel version#6150

Merged
longlho merged 1 commit intomainfrom
fix/bazel-cache
Mar 17, 2026
Merged

fix(deps): disable bazelisk cache to fix stale Bazel version#6150
longlho merged 1 commit intomainfrom
fix/bazel-cache

Conversation

@longlho
Copy link
Member

@longlho longlho commented Mar 17, 2026

Problem

CI is running Bazel 8.1.0 despite .bazelversion specifying 9.0.1. The setup-bazel bazelisk cache was poisoned — it cached the Bazel 8.1.0 binary under the hash for .bazelversion content 9.0.1, and every subsequent run restores the wrong binary.

This causes aspect_rules_js v3 upgrade (#6135) to fail because Bazel 8.1.0 doesn't support repo_name = None in bazel_dep().

Fix

Disable bazelisk-cache in all 6 workflows. Bazelisk download is ~2-3 seconds, so the cache savings are negligible compared to the risk of version mismatch.

Affected workflows

  • .github/workflows/test.yml (2 jobs)
  • .github/workflows/verify-hooks.yml
  • .github/workflows/release.yml
  • .github/workflows/rust-cli-release.yml
  • .github/workflows/website.yml
  • .github/workflows/typesense-index.yml

🤖 Generated with Claude Code

The setup-bazel bazelisk cache is serving Bazel 8.1.0 despite
.bazelversion specifying 9.0.1. The cache was poisoned — the
cached binary doesn't match the version file hash. Disabling the
cache lets bazelisk download the correct version each time.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@longlho longlho enabled auto-merge (squash) March 17, 2026 18:00
@longlho longlho merged commit 612eb64 into main Mar 17, 2026
6 checks passed
@longlho longlho deleted the fix/bazel-cache branch March 17, 2026 18:01
longlho added a commit that referenced this pull request Mar 17, 2026
Reverts the bazelisk-cache: false change from #6150 — the root cause
was .bazeliskrc pinning USE_BAZEL_VERSION=8.1.0, not a stale cache.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant