build: update bazel dependencies (main)

[angular-robot]

This PR contains the following updates:

Package	Type	Update	Change
aspect_rules_esbuild	bazel_dep	minor	0.23.0 -> 0.24.0
rules_angular	git_override	digest	1f1aa3e -> b97a21c

---

Release Notes

aspect-build/rules_esbuild (aspect_rules_esbuild)

v0.24.0

Using Bzlmod with Bazel 6:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_esbuild", version = "0.24.0")

Using WORKSPACE

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_esbuild",
    sha256 = "53dfd354cc6261aaa7717d9f2267f30ab2247d389d1f585780333b0da8e9de1a",
    strip_prefix = "rules_esbuild-0.24.0",
    url = "https://github.com/aspect-build/rules_esbuild/releases/download/v0.24.0/rules_esbuild-v0.24.0.tar.gz",
)

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

# rules_esbuild setup #
######################

# Fetches the rules_esbuild dependencies.

# If you want to have a different version of some dependency,
# you should fetch it *before* calling this.

# Alternatively, you can skip calling this function, so long as you've
# already fetched all the dependencies.
load("@​aspect_rules_esbuild//esbuild:dependencies.bzl", "rules_esbuild_dependencies")

rules_esbuild_dependencies()

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

rules_js_register_toolchains(node_version = DEFAULT_NODE_VERSION)

# Register a toolchain containing esbuild npm package and native bindings
load("@​aspect_rules_esbuild//esbuild:repositories.bzl", "LATEST_ESBUILD_VERSION", "esbuild_register_toolchains")

esbuild_register_toolchains(
    name = "esbuild",
    esbuild_version = LATEST_ESBUILD_VERSION,
)

To use rules_esbuild with bazel-lib 2.0, you must additionally register the coreutils toolchain.

load("@​aspect_bazel_lib//lib:repositories.bzl", "register_coreutils_toolchains")
register_coreutils_toolchains()

What's Changed

• chore: add jbedard to bcr maintainers by @​jbedard in #​238
• chore: remove BCR homepage, as we now use the BCR UI itself by @​alexeagle in #​239
• always set 'use_default_shell_env' in ctx.actions.run by @​malt3 in #​215
• chore: mirror external releases by @​shYkiSto in #​240
• fix: remapping of relative-path imports marked external that don't correspond to a filesystem path in sandbox by @​Strum355 in #​201
• fix: ESBUILD_BINARY_PATH re-pathing inside launcher by @​alexeagle in #​242
• feat: allow users to give an unknown version of esbuild by @​alexeagle in #​241
• chore: cleanup CI and BCR config by @​alexeagle in #​243

New Contributors

• @​malt3 made their first contribution in #​215
• @​shYkiSto made their first contribution in #​240

Full Changelog: aspect-build/rules_esbuild@v0.23.0...v0.24.0

---

Configuration

📅 Schedule: Branch creation - "after 6am and before 10am on Monday, Wednesday, Friday" in timezone Europe/Rome, 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.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     conflicts with base branch "main"
     status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[ngbot]

I see that you just added the action: merge label, but the following checks are still failing:
     conflicts with base branch "main"
     status "mergeability" is failing
If you want your PR to be merged, it has to pass all the CI checks.
If you can't get the PR to a green state due to flakes or broken main, please try rebasing to main and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

[alan-agius4]

This PR was merged into the repository. The changes were merged into the following branches:

• main: 12146a2