Jon Brandvein

This flag doesn't actually exist at head yet, will submit the code shortly. Then we'll check the pipeline and confirm it's feasible to flip for 6.0.

I believe so. I hit a snag that I need to create a second incompatible flag to flip alongside it, but I don't believe that'll stop me.

Yes, it looks like bazel_tools needs to atomically switch to the new public syntax, and then we can see if there are any remaining breakages downstream (using runs that also...

We are actively interested in (i.e., designing this quarter) a feature for `load()`-level enforcement of .bzl visibility. This would not include separate visibility declarations for individual symbols within a .bzl...

Update: Currently working on a design doc, expect to share it in a week or so.

Update: We're actively implementing a simplified prototype, but the real design is not finalized.

Update: We've been working on a design and implementation, and are aiming to include this in 6.0 (to be cut in ~a week).

Yes, and I'm about to add a third blocking flag as well. (Logically these are all the same flag though, in terms of the amount of migration work they represent.)...

Update: Incompatible flags are submitted, will run downstream pipeline to see about flipping them. Other implementation commits to come shortly.

Hm, best reopen this as release blocker until I submit the documentation as well.