MODULE.bazel pins [email protected] and [email protected] — neither works under Bazel 8
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- wasm
- Domain
- build-system
Research direction
Start in rules_haskell's MODULE.bazel and inspect the rules_sh and aspect_rules_js pins, then run bazel mod graph under Bazel 8. Check the asterius extension's use of @aspect_rules_js//npm:npm_import.bzl and determine the compatible pin or required adaptation. Done means the module graph resolves without downstream single_version_override workarounds.
Written by the indexing model from the issue text.
Description
Hi! Reporting from a downstream Bazel 8 (Aspect fork) consumer.
After PR #2394 (2026-03-25) landed the Bazel 8 core-semantics fix, the direct incompatibility at HEAD is the transitive bzlmod pins inside rules_haskell's own MODULE.bazel:
[email protected]— callsget_cpu_value, removed in Bazel 8. Fixed in[email protected](2024). Just needs a version bump.[email protected]— the asterius extension top-level-loads@aspect_rules_js//npm:npm_import.bzl, which[email protected]removed. Either bump to 2.x and adapt or version-pin 1.x.
Both blow up at bazel mod graph time before any compilation starts, so downstream single_version_override workarounds are the only way to consume HEAD on Bazel 8 today.
For now we're patching downstream via single_version_override(rules_sh, 0.5.0) + dropping the asterius wiring entirely (we don't need WebAssembly). Happy to send a PR if useful, but logging the issue first so others can find it.
Filed by an internal monorepo (Datavant) ramp-up of rules_haskell; not blocking us, just blocking our patches from going away.
- Dominant language
- Starlark
- Stars
- 279
- Forks
- 94
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tweag/rules_haskell
-
cc_wrapper crashes with ValueError on Windows when a path is on another drivePossibly taken @TrapsterDK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
tweag/rules_haskell#2492 ·
Maintainers usually reply within 1 day
-
Prepare release 1.1Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
tweag/rules_haskell#2467 ·
Maintainers usually reply within 1 day
-
Track CI failuresOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
tweag/rules_haskell#2456 · 96 comments ·
Maintainers usually reply within 1 day
-
type: feature request
Difficulty 5/5 Over a week Newbie friendliness 25/100
tweag/rules_haskell#2451 ·
Maintainers usually reply within 1 day
-
os:windows type: bug
Difficulty 4/5 3-5 days Newbie friendliness 50/100
tweag/rules_haskell#2447 · 2 comments ·
Maintainers usually reply within 1 day
All issues in tweag/rules_haskell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Netcracker/qubership-authz-agent#311 ·
Maintainers usually reply within 1 day
-
deploy-image adds Recorder to the wrong reconciler when another controller name ends with the kindOpenrelease-blocker
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kubernetes-sigs/kubebuilder#6191 ·
Maintainers usually reply within 1 day
-
Pin Python to 3.14 in the era5grib-parallel environment specificationPossibly taken @atteggiani claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ACCESS-NRI/containerised-environments-infra#129 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
briandconnelly/data-reasoning#106 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/skill-recorder#113 · 1 reaction ·
Maintainers usually reply within 1 day