build: update bazel packages

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@bazel/jasmine	devDependencies	minor	1.6.1 -> 1.7.0
@bazel/karma	devDependencies	minor	1.6.1 -> 1.7.0
@bazel/labs	devDependencies	minor	1.6.1 -> 1.7.0
@bazel/typescript	devDependencies	minor	1.6.1 -> 1.7.0
bazel_toolchains	http_archive	minor	3.1.2 -> 3.2.0
build_bazel_rules_nodejs	http_archive	minor	1.6.1 -> 1.7.0

---

Release Notes

bazelbuild/rules_nodejs

v1.7.0

Compare Source

To upgrade:

http_archive(
    name = "build_bazel_rules_nodejs",
    sha256 = "84abf7ac4234a70924628baa9a73a5a5cbad944c4358cf9abdb4aab29c9a5b77",
    urls = ["https://github.com/bazelbuild/rules_nodejs/releases/download/1.7.0/rules_nodejs-1.7.0.tar.gz"],
)

and update all your @​bazel-scoped npm packages to the matching versions.
yarn: yarn upgrade --scope @​bazel
npm: there is no built-in command but you can try npx update-by-scope @​bazel

Features

• angular: introduce an Angular CLI builder (5ac842e)

Bug Fixes

• backport Windows fix from master branch (24cb37e)
• builtin: fix linker common path reduction bug where reduced path conflicts with node_modules (3b5350b)
• builtin: rerun yarn_install and npm_install when node version changes (81bba0c)
• labs: handle const/let syntax in generated protoc js (54cae78)

bazelbuild/bazel-toolchains

v3.2.0

Compare Source

SHA256:db48eed61552e25d36fe051a65d2a329cc0fb08442627e8f13960c5ab087a44e

---

Renovate configuration

📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

🚦 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 WhiteSource Renovate. View repository job log here.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}