Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automation for rake-compiler-dock releases? #308

Open
gjtorikian opened this issue Jan 4, 2024 · 1 comment
Open

Automation for rake-compiler-dock releases? #308

gjtorikian opened this issue Jan 4, 2024 · 1 comment

Comments

@gjtorikian
Copy link
Contributor

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 #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:

  1. A GitHub action that runs on a daily cron, to
  2. Check to see if there's a new rake-compiler -dock release, and if so
  3. Open a PR which changes all the necessary Dockerfiles to match the M.m.p version

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.

@ianks
Copy link
Collaborator

ianks commented Feb 5, 2024

Yeah I'm definitely game for this 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants