chore(release): trigger pinakes-docker image rebuild on stable release#189
Conversation
After publishing a stable release, fire a repository_dispatch to fabiodalez-dev/pinakes-docker so it rebuilds and republishes the Docker image for the new version. Guarded to stable releases, non-fatal (the Docker repo also polls daily as a safety net).
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughIn ChangesDocker rebuild trigger post-release
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adds a non-fatal hook at the end of
scripts/create-release.shthat, after a stable release is published, fires arepository_dispatch(eventpinakes_release, payloadpinakes_version) to the new fabiodalez-dev/pinakes-docker repo so it rebuilds and republishes the multi-arch Docker image for that version.ghdispatch fails, it prints the manual command and the release still succeeds. The Docker repo also runs a daily poller as a safety net.create-release.shis a dev-only tool, excluded from the release ZIP.Summary by CodeRabbit
Release Notes