Open Yannic opened 5 years ago
@iirina Can you add the labels breaking-change-1.0
, incompatible-change
, migration-ready
, and migration-0.29
per https://docs.bazel.build/versions/0.28.0/backward-compatibility.html#github-labels? Thanks!
@Yannic done! Thanks!
Will the migration tooling be available to do the migration? (based on buildifier)
Yes, a buildifier fix has been added in https://github.com/bazelbuild/buildtools/pull/674
This flag won't be flipped in Bazel 1.0. Could someone remove breaking-change-1.0
?
Hi Yannic, I had to make a decision whether to flip this flag (and similar flags for C++, Java, and Python) in case we have 2.0 in December, and I said we shouldn't (the ecosystem is not yet ready). I hope you agree with that.
What is the status of this flag, it is saying will be flipped TBD but breaking change 5.0. Is it flipped in Bazel 5?
@philwo I assume we are not flipping this in 5.0 since we decided to go with builtin Starlark rules instead for the time being?
/cc @comius
I don't think it's ready for flipping in 5.0 (would like to do it eventually though)
Absolutely, not flipping in 5.0. I removed the label on the issue.
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage
) if you think this issue is still relevant or you are interested in getting the issue resolved.
Flag:
--incompatible_load_proto_rules_from_bzl
Available since: 0.29 Will be flipped in: TBD Tracking issue: #8891proto_library
andproto_lang_toolchain
have to be loaded from @rules_proto.For example, if you are using
proto_library
, add the following load statement to your BUILD/bzl file.You can use the following buildifier command to automate the changes to your BUILD/bzl files:
You will have to add
proto_library
to your WORKSPACE file as well: