Breaking experience: Difference in how Lage processes dependency graph post 0.32 about lage

[kenotron]

The laxed implementation was definitely not intentional in the first place! I'm going to take a look at making a repro as a test for future fix here. I'll work to restore that functionality ASAP.

[GiriB]

Thanks @kenotron ! If we believe that the strictness is the right thing to do, then that also makes sense to me. Yes, it'll be bit of work - teams would have to fix their build graphs, but I think that is a good thing.

I'll let Lage team decide what's the right future here, but either ways, adding an example in documentation to clarify what is intended and what's not would be great!!

[kenotron]

So I think restoring default behavior is imperative - we can add a "--strict" or whatever to enforce many strictness things like file access, etc.

[kenotron]

Update 1: alright, locally I have a e2e test written with your case! (thanks for the small repro repo)

[kenotron]

Update 2: this is fixed in my latest (failed test is now green :))