Bazel WORKSPACE vs MODULE.bazel dependency conflict

Inconsistent transitive dependency version when WORKSPACE and MODULE.bazel coexist

0 reputation · 18 Oct 2023, 07:15 UTC

97.2K views0

Ensure that a Bazel build produces identical external dependency graphs across developer machines when a project contains both a WORKSPACE file and a MODULE.bazel file during the migration to Bzlmod.

The effective version of a transitive dependency may differ depending on the Bazel release, the presence of local override files, or whether the experimental Bzlmod flag is enabled, leading to non‑repeatable builds across teams.

Which file takes precedence when both are present? Does enabling the --experimental_bzlmod flag alter this precedence? Are there specific .bazelrc settings that force consistent resolution?

2,368 following

Keep exploring this topic

Bzlmod module resolution transition from WORKSPACE in Bazel 6+

Bazel 6+ prioritizes MODULE.bazel over WORKSPACE, but mixed mode behavior varies by version and no WORKSPACE deprecation timeline is finalized, creating uncertainty for repeatable builds.

local_repository vs http_archive for Private Dependencies Under Hermetic Sandbox

Choosing between local_repository path shortcuts and http_archive fetches for private dependencies when hermetic sandboxing breaks local-only configurations in production CI and remote execution.

Platform requirement mismatch during runtime execution in Composer 2

Exploring the conflict between config.platform overrides and runtime platform checks in Composer 2, and how to prevent resolution success from masking runtime extension failures.

Does PacletInfo.m allow specifying exact versions for paclet dependencies?

Question about whether PacletInfo.m can specify exact paclet dependency versions to enable reproducible Wolfram Language environments.

Inconsistent transitive dependency version when WORKSPACE and MODULE.bazel coexist

0 answers

Your perspective belongs here.

0 question comments