chore(deps): update dependency aspect_rules_js to v3#6135
Merged
Conversation
Member
|
CI failure is an upstream bug in Blocked until upstream releases a fix. |
longlho
added a commit
that referenced
this pull request
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](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Member
|
@renovate rebase |
a3ad32c to
8d28531
Compare
longlho
added a commit
that referenced
this pull request
Mar 17, 2026
## Problem `.bazeliskrc` has `USE_BAZEL_VERSION=8.1.0` which **overrides** `.bazelversion` (priority: `.bazeliskrc` > `.bazelversion`). This means all CI and local builds have been running Bazel 8.1.0 despite `.bazelversion` being bumped to 9.0.1 in #6077. This is the root cause of #6135 failing — `aspect_rules_js@3.0.3` uses `repo_name = None` which requires Bazel >=7.6 but works differently on 8.x vs 9.x. ## Fix Update `USE_BAZEL_VERSION` in `.bazeliskrc` to `9.0.1` to match `.bazelversion`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
8d28531 to
ca4a330
Compare
In rules_js v3, ts_project and js_run_binary auto-copy srcs to bin, causing conflicting actions when multiple targets use the same source files. Fix by creating a single shared copy_to_bin target for all source/public files that all targets reference. 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
1 participant
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.
This PR contains the following updates:
2.9.2→3.0.3Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.