Skip to content

build: update bazel dependencies (main)#33503

Open
angular-robot wants to merge 1 commit into
angular:mainfrom
angular-robot:ng-renovate/main-bazel-dependencies
Open

build: update bazel dependencies (main)#33503
angular-robot wants to merge 1 commit into
angular:mainfrom
angular-robot:ng-renovate/main-bazel-dependencies

Conversation

@angular-robot

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
bazel_lib bazel_dep minor 3.3.13.4.0
rules_nodejs bazel_dep patch 6.7.46.7.5

  • If you want to rebase/retry this PR, check this box

Release Notes

bazel-contrib/rules_nodejs (rules_nodejs)

v6.7.5

Using Bzlmod with Bazel 6 or greater

  1. (Bazel 6 only) Enable with common --enable_bzlmod in .bazelrc.
  2. Add to your MODULE.bazel file:
bazel_dep(name = "rules_nodejs", version = "6.7.5")

Using WORKSPACE

Paste this snippet into your WORKSPACE.bazel file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "rules_nodejs",
    sha256 = "5e803a42bd0af134529f0724edb4d26e295e3c17a0af0655e5265250c82ce9b5",
    strip_prefix = "rules_nodejs-6.7.5",
    url = "https://github.com/bazel-contrib/rules_nodejs/releases/download/v6.7.5/rules_nodejs-v6.7.5.tar.gz",
)

What's Changed

Full Changelog: bazel-contrib/rules_nodejs@v6.7.4...v6.7.5

See associated pull request for more information.
@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only] labels Jul 2, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates rules_nodejs to version 6.7.5 and bazel_lib to version 3.4.0 in MODULE.bazel, along with corresponding updates in MODULE.bazel.lock. However, a critical issue was identified where the rules_nodejs module extension was completely removed from the lockfile, which will cause Bazel builds to fail in strict lockfile environments. To resolve this, the lockfile should be regenerated by running bazel mod tidy.

Comment thread MODULE.bazel.lock
]
}
},
"@@rules_nodejs+//nodejs:extensions.bzl%node": {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The rules_nodejs module extension (@@rules_nodejs+//nodejs:extensions.bzl%node) has been completely removed from the lockfile in this PR. Since this extension is actively used in MODULE.bazel (lines 40-61 and 63-129) to configure Node.js toolchains and export repositories, removing it will cause Bazel builds to fail in CI environments where strict lockfile checks are enforced (e.g., --lockfile_mode=error or --lockfile_mode=strict).

This often happens when dependency update bots (like Renovate) perform partial lockfile updates without fully evaluating all module extensions.

How to fix:
Please regenerate the lockfile locally by running:

bazel mod tidy

or by running a dummy build to force extension evaluation:

bazel build --nobuild //...

This will ensure that the node extension and its generated repository specs are correctly recorded in MODULE.bazel.lock.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: automation This PR is targeted to only merge into the branch defined in Github [bot use only]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant