oxidize-rb
Automation for `rake-compiler-dock` releases?
I really hate the fact that Ruby major versions release on Dec 25. It's always a PITA for maintainers of gems, and every year, even though I prepare to cut a few new gems, I get caught off guard with a new surprising issue.
I was thinking about how to reduce human involvement to prevent something like https://github.com/oxidize-rb/rb-sys/pull/298 happening again. Let me reiterate that I don't think this dependency update not being released was anyone's "fault," at all; this is not a postmortem or anything of the sort! But I want to strengthen the gem ecosystem by minimizing rote tasks like updating the version number in various Dockerfiles. rb-sys now has various downstream consumers, and, selfishly, I am one of them.
With that I propose:
- A GitHub action that runs on a daily cron, to
- Check to see if there's a new
rake-compiler -dockrelease, and if so - Open a PR which changes all the necessary Dockerfiles to match the
M.m.pversion
Happy to do the work to do this if it's desired! Just throwing the idea out there. ☮️ This of course won't solve the issue entirely—the new builds still need to be pushed—but it's a start.
