MODULE.bazel pins [email protected] and [email protected] — neither works under Bazel 8

Open
#2,426 1 comment 0 reactions 0 assignees View on GitHub

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:

  1. [email protected] — calls get_cpu_value, removed in Bazel 8. Fixed in [email protected] (2024). Just needs a version bump.
  2. [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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tweag/rules_haskell

All issues in tweag/rules_haskell

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.