I'm just opening this issue to start off some discussions. I'm happy to work further on this. I've seen that there are some people that are already looking into using this once it's done with is very encouraging. Here are a few points that I think it would be good to get folks' opinion on:

1. where should schedule.json live? Here I see basically 3 options:
   a.) have it as a file in the repo that gets updated regularly.
   b.) include it as a release artefact that can be published quarterly
   c.) Have CI do the calculation from scratch every time
   Personally I like the idea of option b since that gives a bit of an easier way to trace it over time, but I'm open to either. Code wise b is also the easiest, though I think all options are possible. I must say not a fan of C since then you don't get a paper trail, but I'm happy with whatever folks from the org like best

2. How do we provide the actions? The lowest burden would be basically an example as currently is in the repo, but I think people would benefit from a copy-and-paste-able solution. I don't think making an action that opens a PR with the updates for some of the major package managers is very hard (I can think of pip, conda, pixi and poetry off the top of my head). I'm happy to build these, and I don't expect to go anywhere, but I'm not sure how folks in the org think of the maintenance burden so I'm happy to listen to feedback here.

Let me know what you think, and if there are any other issues that need to be discussed! Excited for this to move forward!