-
-
Notifications
You must be signed in to change notification settings - Fork 102
refactor: Minor compatibility fixes #1044
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
base: main
Are you sure you want to change the base?
refactor: Minor compatibility fixes #1044
Conversation
According to the Bazel documentation, this option has already been deprecated for quite a long time. It already defaults to True.
Ever since Bazel 7.2, the officially documented method for accessing the host constraints is to load @platforms//host:constraints.bzl. More details: https://bazel.build/extending/platforms#specifying-build-platform https://bazel.build/concepts/platforms#default-platforms
Ever since bzlmod, @// has lost any official meaning: https://bazel.build/concepts/labels Bazel still seems to allow it, but given the fact that this format is no longer documented we should stop using it. In this specific case it also doesn't matter. As long as we provide a label that is valid.
Friendly ping! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
Hm, we still support Bazel 6 in bazel-lib 2.x, and CI failure there is
Maybe we still need |
@EdSchouten we're playing with https://github.com/google/triage-party today. It says I should ask you to merge - even though I should probably do the work myself :) |
I am writing an experimental analysis tool that is capable of parsing BUILD/.bzl files. In the process I ran into some minor issues processing some of the code in bazel-lib. In many cases I obviously fixed up my tool, but I was left with some breakages where I think it makes sense to alter bazel-lib instead, because the Bazel documentation indicates that the feature at hand is deprecated. Merging such changes prevent potential breakages in the future.