The issue I've had is not just the hundred upgrades, but also that as time passes, it may not even be feasible to solve the dependency constraints for bumping a single package without a huge amount of archaeological work.
Yeah, I'm pretty nervous about an aspect of that, given that some of Querki's dependencies are ~8 years old. I've already had to deal with dead repositories a few times as it is; I'm hoping I don't get too badly tripped up by that.
The "lockstep" problem tends not to be too bad with the stacks that I've been using -- it's not a non-issue, but much of the Scala world is pretty good about keeping dependencies somewhat loose. There are exceptions (at work, the upgrade to ZIO 2 was absolutely hellish because it required updating the entire world at once), but I'm keeping my fingers crossed when it comes to Querki's requirements.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2025-01-05 06:49 pm (UTC)Yeah, I'm pretty nervous about an aspect of that, given that some of Querki's dependencies are ~8 years old. I've already had to deal with dead repositories a few times as it is; I'm hoping I don't get too badly tripped up by that.
The "lockstep" problem tends not to be too bad with the stacks that I've been using -- it's not a non-issue, but much of the Scala world is pretty good about keeping dependencies somewhat loose. There are exceptions (at work, the upgrade to ZIO 2 was absolutely hellish because it required updating the entire world at once), but I'm keeping my fingers crossed when it comes to Querki's requirements.