#go.mod noise
1 messages · Page 1 of 1 (latest)
I'm guessing it would've been related to this particular change, which seems like we're running go mod tidy unconditionally? https://github.com/dagger/dagger/pull/11962/changes#diff-799c62755e728b5e47da423b829e747704c507f45304124573a13beef8187f90R185
yup it appears so
Would you know if this is something we want to keep going forward?
Whatever the most idiomatic and least annoying behavior, that's what we want 🙂 First step is to determine with full confidence what that is
let me ping @upper seal and @sharp venture (France timezone) for their take when they wake up
other <@&946480760016207902> might have an opinion also
Thanks heaps!
@tiny wharf would you be willing to file a issue github discussion describing the problem you experience, and what you would expect the correct behavior to be?
Sure thing, will do soon
Apologies, it's probably more likely to be this line as the reason it's getting updated: https://github.com/dagger/dagger/commit/249a4a7064493949e52b473699148bb0f0cd5a5f#diff-5f7fef862e511eccab9f0ba16852b444e09767d8093791899b9cba3674c6f7edR253
@tiny wharf We answered with @sharp venture
go.mod noise