Ruby Releases Ruby
summary
Ruby core and packaging now ship far more often with much less toil: CI runs across GitHub Actions and an in-house RubyCI using chkbuild, infrastructure is managed with mitamae, and release steps from tag to S3 publishing, Docker images and announcement drafts are auto-driven. Release frequency rises roughly 2–3x faster release cadence, nearly everything is scripted as automated release pipeline in Ruby, backporting remains partly manual, and gem publishing gains Sigstore-backed gem publishing for traceability.
AI-written summary · about
chapters (20)
- 0:00Introduction and background
- 1:50Ruby releases progress
- 3:45CI infrastructure and RubyCI
- 7:17Human role in CI setup
- 8:44Maintaining Ruby's stability
- 9:30What defines a release
- 10:48Automating Ruby releases
- 12:20Security release improvements
- 13:01Ruby tool development cycle
- 14:30Automated release notes
- 15:59Release workflow automation
- 16:48RubyGems and Bundler 4.0
- 18:23RubyGems 4.1 features
- 20:37Bundler plugin challenges
- 23:18OIDC trusted publisher
- 25:59Sigstore for gem releases
- 26:43RubyGems backport automation
- 28:15Challenges in backporting
- 29:43Future of secure releases
- 30:08Human vs AI in development
