Skip to content

Conversation

angular-robot
Copy link
Collaborator

@angular-robot angular-robot commented Jul 9, 2025

This PR contains the following updates:

Package Type Update Change
aspect_rules_js http_archive minor v2.3.8 -> v2.4.2
rules_browsers git_repository digest 56ef800 -> c3f7358

Release Notes

aspect-build/rules_js (aspect_rules_js)

v2.4.2

Compare Source

Many companies are successfully building with rules_js.
If you're getting value from the project, please let us know!
Just comment on our Adoption Discussion.

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_js", version = "2.4.2")

####### Node.js version #########

### By default you get the node version from DEFAULT_NODE_VERSION in @​rules_nodejs//nodejs:repositories.bzl
### Optionally you can pin a different node version:
bazel_dep(name = "rules_nodejs", version = "6.3.0")
node = use_extension("@​rules_nodejs//nodejs:extensions.bzl", "node", dev_dependency = True)
node.toolchain(node_version = "16.14.2")

#################################

npm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "npm", dev_dependency = True)

npm.npm_translate_lock(
    name = "npm",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

use_repo(npm, "npm")

pnpm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "pnpm")

### Allows developers to use the matching pnpm version, for example:
### bazel run -- @​pnpm --dir /home/runner/work/rules_js/rules_js install
use_repo(pnpm, "pnpm")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "aspect_rules_js",
    sha256 = "b71565da7a811964e30cccb405544d551561e4b56c65f0c0aeabe85638920bd6",
    strip_prefix = "rules_js-2.4.2",
    url = "https://github.com/aspect-build/rules_js/releases/download/v2.4.2/rules_js-v2.4.2.tar.gz",
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

load("@​aspect_rules_js//npm:repositories.bzl", "npm_translate_lock")

npm_translate_lock(
    name = "npm",
    npmrc = "//:.npmrc",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

load("@​npm//:repositories.bzl", "npm_repositories")

npm_repositories()

What's Changed

Full Changelog: https://github.com/aspect-build/rules\_js/compare/v2.4.1...v2.4.2

v2.4.1

Compare Source

Many companies are successfully building with rules_js.
If you're getting value from the project, please let us know!
Just comment on our Adoption Discussion.

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_js", version = "2.4.1")

####### Node.js version #########

### By default you get the node version from DEFAULT_NODE_VERSION in @​rules_nodejs//nodejs:repositories.bzl
### Optionally you can pin a different node version:
bazel_dep(name = "rules_nodejs", version = "6.3.0")
node = use_extension("@​rules_nodejs//nodejs:extensions.bzl", "node", dev_dependency = True)
node.toolchain(node_version = "16.14.2")

#################################

npm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "npm", dev_dependency = True)

npm.npm_translate_lock(
    name = "npm",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

use_repo(npm, "npm")

pnpm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "pnpm")

### Allows developers to use the matching pnpm version, for example:
### bazel run -- @​pnpm --dir /home/runner/work/rules_js/rules_js install
use_repo(pnpm, "pnpm")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "aspect_rules_js",
    sha256 = "ca638e0aa33b087706bc7f5e887ce01cdf6ec82de00660f22409fa8be34a8ce2",
    strip_prefix = "rules_js-2.4.1",
    url = "https://github.com/aspect-build/rules_js/releases/download/v2.4.1/rules_js-v2.4.1.tar.gz",
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

load("@​aspect_rules_js//npm:repositories.bzl", "npm_translate_lock")

npm_translate_lock(
    name = "npm",
    npmrc = "//:.npmrc",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

load("@​npm//:repositories.bzl", "npm_repositories")

npm_repositories()

What's Changed

New Contributors

Full Changelog: https://github.com/aspect-build/rules\_js/compare/v2.4.0...v2.4.1

v2.4.0

Compare Source

Many companies are successfully building with rules_js.
If you're getting value from the project, please let us know!
Just comment on our Adoption Discussion.

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_js", version = "2.4.0")

####### Node.js version #########

### By default you get the node version from DEFAULT_NODE_VERSION in @​rules_nodejs//nodejs:repositories.bzl
### Optionally you can pin a different node version:
bazel_dep(name = "rules_nodejs", version = "6.3.0")
node = use_extension("@​rules_nodejs//nodejs:extensions.bzl", "node", dev_dependency = True)
node.toolchain(node_version = "16.14.2")

#################################

npm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "npm", dev_dependency = True)

npm.npm_translate_lock(
    name = "npm",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

use_repo(npm, "npm")

pnpm = use_extension("@​aspect_rules_js//npm:extensions.bzl", "pnpm")

### Allows developers to use the matching pnpm version, for example:
### bazel run -- @​pnpm --dir /home/runner/work/rules_js/rules_js install
use_repo(pnpm, "pnpm")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "aspect_rules_js",
    sha256 = "961393890a58de989ad7aa36ce147fc9b15a77c8144454889bf068bdd12c5165",
    strip_prefix = "rules_js-2.4.0",
    url = "https://github.com/aspect-build/rules_js/releases/download/v2.4.0/rules_js-v2.4.0.tar.gz",
)

load("@​aspect_rules_js//js:repositories.bzl", "rules_js_dependencies")

rules_js_dependencies()

load("@​aspect_rules_js//js:toolchains.bzl", "DEFAULT_NODE_VERSION", "rules_js_register_toolchains")

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

load("@​aspect_rules_js//npm:repositories.bzl", "npm_translate_lock")

npm_translate_lock(
    name = "npm",
    npmrc = "//:.npmrc",
    pnpm_lock = "//:pnpm-lock.yaml",
    verify_node_modules_ignored = "//:.bazelignore",
)

load("@​npm//:repositories.bzl", "npm_repositories")

npm_repositories()

What's Changed

New Contributors

Full Changelog: https://github.com/aspect-build/rules\_js/compare/v2.3.8...v2.4.0


Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@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: rc This PR is targeted for the next release-candidate labels Jul 9, 2025
@angular-robot
Copy link
Collaborator Author

angular-robot commented Jul 9, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined
Command failed: pnpm bazel run //.github/actions/deploy-docs-site:main.update
Loading: 
Loading: 
Loading: 
ERROR: Error computing the main repository mapping: Label '@rules_browsers//setup:step_1.bzl' is invalid because 'setup' is not a package; perhaps you meant to put the colon here: '@rules_browsers//:setup/step_1.bzl'?

File name: undefined
Command failed: pnpm bazel run //packages/common:base_currencies_file.update
Loading: 
ERROR: Error computing the main repository mapping: Label '@rules_browsers//setup:step_1.bzl' is invalid because 'setup' is not a package; perhaps you meant to put the colon here: '@rules_browsers//:setup/step_1.bzl'?

File name: undefined
Command failed: pnpm bazel run //packages/common/locales:closure_locale_file.update
Loading: 
ERROR: Error computing the main repository mapping: Label '@rules_browsers//setup:step_1.bzl' is invalid because 'setup' is not a package; perhaps you meant to put the colon here: '@rules_browsers//:setup/step_1.bzl'?

File name: undefined
Command failed: pnpm bazel run //packages/core:base_locale_file.update
Loading: 
ERROR: Error computing the main repository mapping: Label '@rules_browsers//setup:step_1.bzl' is invalid because 'setup' is not a package; perhaps you meant to put the colon here: '@rules_browsers//:setup/step_1.bzl'?

@ngbot ngbot bot added this to the Backlog milestone Jul 9, 2025
@pullapprove pullapprove bot requested a review from thePunderWoman July 9, 2025 10:09
@AndrewKushnir
Copy link
Contributor

@josephperrott it looks like CI is failing for this rules_angular update. Is this PR relevant or those updates will be happening as a part of other PRs?

@AndrewKushnir AndrewKushnir added target: patch This PR is targeted for the next patch release and removed target: rc This PR is targeted for the next release-candidate labels Jul 9, 2025
@AndrewKushnir AndrewKushnir added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Jul 9, 2025
@thePunderWoman thePunderWoman removed the action: merge The PR is ready for merge by the caretaker label Jul 11, 2025
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch from b1f0baf to d65ba89 Compare July 11, 2025 17:09
@angular-robot angular-robot changed the title build: update rules_angular digest to 8bf9ae3 (20.1.x) build: update bazel dependencies (20.1.x) Jul 12, 2025
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch from d65ba89 to 904829f Compare July 12, 2025 22:09
@josephperrott
Copy link
Member

This will become unblocked after #62541 lands

@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch from 904829f to cdd95c6 Compare July 15, 2025 00:54
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch 3 times, most recently from 3a0e66f to 670074c Compare July 25, 2025 22:41
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch 9 times, most recently from 784b354 to 86692f9 Compare August 5, 2025 17:07
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch from 86692f9 to 96b2eca Compare August 6, 2025 13:48
See associated pull request for more information.
@angular-robot angular-robot force-pushed the ng-renovate/20.1.x-bazel-dependencies branch from 96b2eca to f4f609f Compare August 7, 2025 16:45
@angular-robot angular-robot changed the title build: update bazel dependencies (20.1.x) build: update bazel dependencies (20.1.x) - abandoned Aug 11, 2025
@angular-robot
Copy link
Collaborator Author

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants