chore(deps): update dependency aspect_rules_ts to v3.7.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
aspect_rules_ts (source)	bazel_dep	patch	3.7.0 -> 3.7.1

---

Release Notes

aspect-build/rules_ts (aspect_rules_ts)

v3.7.1

Using Bzlmod:

Add to your MODULE.bazel file:

bazel_dep(name = "aspect_rules_ts", version = "3.7.1")

rules_ts_ext = use_extension("@​aspect_rules_ts//ts:extensions.bzl", "ext", dev_dependency = True)

rules_ts_ext.deps(
    ts_version_from = "//:package.json",
)

use_repo(rules_ts_ext, "npm_typescript")

Using legacy WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@​bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
    name = "aspect_rules_ts",
    sha256 = "de34e2c974a4af366e141d343803faee633140322f014f7ea7363d970c702d74",
    strip_prefix = "rules_ts-3.7.1",
    url = "https://github.com/aspect-build/rules_ts/releases/download/v3.7.1/rules_ts-v3.7.1.tar.gz",
)

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

# rules_ts setup #
##################

# Fetches the rules_ts 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_ts//ts:repositories.bzl", "rules_ts_dependencies")

rules_ts_dependencies(
    # This keeps the TypeScript version in-sync with the editor, which is typically best.
    ts_version_from = "//:package.json",

    # Alternatively, you could pick a specific version, or use
    # load("@​aspect_rules_ts//ts:repositories.bzl", "LATEST_TYPESCRIPT_VERSION")
    # ts_version = LATEST_TYPESCRIPT_VERSION
)

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()

# Register aspect_bazel_lib toolchains;

# If you use npm_translate_lock or npm_import from aspect_rules_js you can omit this block.
load("@​aspect_bazel_lib//lib:repositories.bzl", "aspect_bazel_lib_dependencies")

aspect_bazel_lib_dependencies()

To use rules_ts with bazel-lib 2.x, you must additionally register the coreutils toolchain.

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

register_coreutils_toolchains()

What's Changed

• fix: don't use version 0.0.0 by @​alexeagle in #​850
• fix(ci): turn on CI config by @​alexeagle in #​851
• Revert "fix(ci): turn on CI config" by @​alexeagle in #​852
• chore: update tools_telemetry to 0.2.8 by @​jbedard in #​849
• Changes by create-pull-request action by @​github-actions[bot] in #​841
• test: add root+outDir . and ./ tests by @​jbedard in #​854
• chore: remove BCR homepage, as we now use the BCR UI itself by @​alexeagle in #​858
• fix: overridding tsconfig outDir via ts_project(tsconfig) dict by @​jbedard in #​860
• Changes by create-pull-request action by @​github-actions[bot] in #​856
• fix: BCR presubmit requires homepage field by @​alexeagle in #​862

Full Changelog: aspect-build/rules_ts@v3.7.0...v3.7.1

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact 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

Post-upgrade command 'bazel mod tidy' has not been added to the allowed list in allowedCommands