fix(deps): update .bazeliskrc to Bazel 9.0.1#6151
Merged
Conversation
.bazeliskrc had USE_BAZEL_VERSION=8.1.0 which overrides .bazelversion (9.0.1), causing all CI and local builds to use Bazel 8.1.0. Remove .bazeliskrc entirely — .bazelversion is the standard single source of truth for the Bazel version. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
d149ca8 to
55192b5
Compare
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>
Bazel 9 changed canonical repo name format: - http_archive repos: +_repo_rules+ → +http_archive+ - http_file repos: +_repo_rules2+ → +http_file+ Update hardcoded paths in test262 BUILD args and intl-segmenter runfiles resolution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
.bazeliskrchasUSE_BAZEL_VERSION=8.1.0which overrides.bazelversion(priority:.bazeliskrc>.bazelversion). This means all CI and local builds have been running Bazel 8.1.0 despite.bazelversionbeing bumped to 9.0.1 in #6077.This is the root cause of #6135 failing —
aspect_rules_js@3.0.3usesrepo_name = Nonewhich requires Bazel >=7.6 but works differently on 8.x vs 9.x.Fix
Update
USE_BAZEL_VERSIONin.bazeliskrcto9.0.1to match.bazelversion.🤖 Generated with Claude Code