Update dependencies

[rplopes]

No description provided.

[waldyrious]

It would be nice to document the context for why these upgrades were needed. Or was it just an update to keep up with the dependencies' latest versions?

[rplopes]

The latter. We want to keep using this package in new projects, but the packages it brings are getting out of date comparing to declaring them explicitely in those new projects.

[waldyrious]

Thanks for the clarification. In that case we should probably consider integrating some app that proposes these updates automatically. IIUC there are several around. Any reason not to do it, other than lack of time/priority?

[rplopes]

You've guessed it right again 😄. With the workload on specific product features, this is one of those projects that are on a low maintenance work, to be updated only when needed (we've updated this in the context of a new repo for a specific project).

It would be great if in the future we got some budget to do a better maintenance job in this sort of projects. But that sounds like a battle for another day.

[waldyrious]

Thanks. I'll add this to my notes of things we ought to work on regarding maintenance and technical debt.

It would be great if in the future we got some budget to do a better maintenance job in this sort of projects. But that sounds like a battle for another day.

We're apparently in the process of defining the goals for the next quarter, so I'll see if I can squeeze this in ;) I'll let you know if more voices are needed to push for it.