-
-
Notifications
You must be signed in to change notification settings - Fork 220
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 rules_cc to v0.0.13 #389
base: master
Are you sure you want to change the base?
Conversation
dd45b02
to
c03446c
Compare
c2f564d
to
9959a8f
Compare
23180f5
to
1a5dc3a
Compare
1a5dc3a
to
0da6581
Compare
a8b9115
to
0db6c77
Compare
a18fb89
to
dbaa74a
Compare
72b15d7
to
5f2d592
Compare
Tests are failing because we (currently) aim to support Bazel 7.0 and The problematic change for us is I assume we want to update cc: @fmeum edit: filed bazelbuild/rules_cc#254 |
…appropriately `reproducible` was added in Bazel 7.1.0; gating this argument allows older Bazel versions to use rules_cc 0.0.13 and newer. Note that this change (use of `reproducible`) came from Bazel itself in bazelbuild/bazel#22335; it made its way over to `rules_cc` via bazelbuild@c2549f6 (see bazelbuild/bazel@1c4e78a). More context [here](bazel-contrib/toolchains_llvm#389 (comment)).
…appropriately `reproducible` was added in Bazel 7.1.0; gating this argument allows older Bazel versions to use rules_cc 0.0.13 and newer. Note that this change (use of `reproducible`) came from Bazel itself in bazelbuild/bazel#22335; it made its way over to `rules_cc` via bazelbuild@c2549f6 (see bazelbuild/bazel@1c4e78a). More context [here](bazel-contrib/toolchains_llvm#389 (comment)).
5f2d592
to
bd92b64
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
This comment was marked as resolved.
This comment was marked as resolved.
I'll look into the rules_cc failures. In WORKSPACE land, it should depend on protobuf via its legacy name |
This PR contains the following updates:
0.0.9
->0.0.13
0.0.9
->0.0.13
Release Notes
bazelbuild/rules_cc (rules_cc)
v0.0.13
Compare Source
What's Changed
New Contributors
Full Changelog: bazelbuild/rules_cc@0.0.12...0.0.13
v0.0.12
Compare Source
Full Changelog: bazelbuild/rules_cc@0.0.11...0.0.12
v0.0.11
Compare Source
Loading rules_cc
What's Changed
New Contributors
Full Changelog: bazelbuild/rules_cc@0.0.10...0.0.11
v0.0.10
Compare Source
What's Changed
Full Changelog: bazelbuild/rules_cc@0.0.9...0.0.10
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.