Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @bazel/labs to v3.8.0 - autoclosed #1382

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 28, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@bazel/labs 3.7.0 -> 3.8.0 age adoption passing confidence

Release Notes

bazelbuild/rules_nodejs

v3.8.0

Compare Source

Upgrade with

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

and update @bazel-scoped npm packages

Features

@bazel/worker package no longer checks whether the major version of rules_nodejs matches what it was built against.
Needed for our 4.0.0 release so that dependencies like the worker mode of rules_sass doesn't throw.

Bug Fixes
  • remove current directory prefix when running from execroot (6be5186)
  • builtin: correctly calculate pkg._directDependency when a mapped node_module is used (9e23f8a)
  • labs: fix ts_proto_library handling of external proto_library (57c6576)
  • runfiles: don't use false as a no-error value (#​2837) (be8b27c)
  • typescript: do not re-declare .json output files in srcs if they are already generated files (6508c6a)
  • typescript: document tsc_test for typecheck-only (bc4d34a)
  • typescript: fix bug in ts_project (write_tsconfig_rule) when extending from a generated tsconfig in same folder (10cca5c)

Configuration

📅 Schedule: "every weekend" in timezone Asia/Hong_Kong.

🚦 Automerge: Disabled due to failing status checks.

Rebasing: Whenever PR becomes conflicted, 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch 29 times, most recently from 338afcc to 827beec Compare September 4, 2021 02:49
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch from 827beec to ff4e9f4 Compare September 4, 2021 04:13
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch 8 times, most recently from bdc5744 to fb7e066 Compare October 10, 2021 17:37
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch 10 times, most recently from bebb3c9 to b281ad3 Compare October 19, 2021 04:13
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch from b281ad3 to 0abfe92 Compare October 25, 2021 03:24
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch 2 times, most recently from 5104338 to 7610402 Compare November 12, 2021 21:59
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch from 7610402 to 128a73f Compare November 28, 2021 08:17
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch 3 times, most recently from 246d143 to 55c7daf Compare December 10, 2021 05:13
@renovate renovate bot force-pushed the renovate/bazel-labs-3.x branch from 55c7daf to a718cd0 Compare December 10, 2021 10:08
@renovate renovate bot changed the title chore(deps): update dependency @bazel/labs to v3.8.0 chore(deps): update dependency @bazel/labs to v3.8.0 - autoclosed Dec 13, 2021
@renovate renovate bot closed this Dec 13, 2021
@renovate renovate bot deleted the renovate/bazel-labs-3.x branch December 13, 2021 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant