either way I think we should be careful to do such upgrades in a pants dev release so it’s not just part of a pants patch release. that said, there’s always the option to pin a tool version in order to make a tool upgrade != pants upgrade.
but yes, it is considered breaking changes, as that PR is labeled “user api change”.
04/24/2023, 11:19 AM
ah, yep, I see how it fits together now, thanks
04/24/2023, 12:55 PM
It's certainly a tradeoff, with neither option being ideal.
But in the end, the reason we provide default resolves for these tools is so users can get the latest and greatest without worrying about the how
04/24/2023, 3:54 PM
Yeah, we should probably have a policy about this...