if ci_badges.map(&:color).detect { it != "green"} ☝️ let me know, as I may have missed the discord notification.

if ci_badges.map(&:color).all? { it == "green"} 👇️ send money so I can do more of this. FLOSS maintenance is now my full-time job.

kettle-family coordinates repeated maintenance workflows across related Ruby gems. It can discover member gems, order them by dependency or explicit hints, run shared check/test/lint/docs/template workflows, bump aligned versions, and drive release preparation or publishing.

Families can be monorepos, sibling repository workspaces, or a single flat gem that releases from several long-lived branches. For branch-stacked gems, release.target_branches lists the branches to process; the release workflow checks each branch out sequentially, rediscovers that branch's gem metadata, and runs the normal flat-repo release flow.

Publish runs are resumable. Before invoking kettle-release, kettle-family checks whether the current gem/version is already published and skips it when it is, avoiding duplicate release-prep commits after a failure/fix/retry cycle. kettle-release runs its own kettle-pre-release gate for full publish flows; options such as start_step=N and --local-ci pass through, CI failures still abort by default, and gem signing passphrases are cached once per family run while RubyGems MFA prompts remain interactive.

Tokens to Remember
Works with JRuby
Works with Truffle Ruby
Works with MRI Ruby 4
Works with MRI Ruby 3
Support & Community
Source
Documentation
Compliance
Style
Maintainer 🎖️
... 💖	🧊 🐙 🛖 🧪

Compatible with MRI Ruby 3.2.0+, and concordant releases of JRuby, and TruffleRuby. CI workflows and Appraisals are generated for MRI Ruby 3.2.0+. This test floor is configured by ruby.test_minimum in .kettle-jem.yml and may be higher than the gem's runtime compatibility floor when legacy Rubies are not practical for the current toolchain.

Find this repo on federated forges (Coming soon!)

Federated DVCS Repository	Status	Issues	PRs	Wiki	CI	Discussions
🧪 kettle-dev/kettle-family on GitLab	The Truth	💚	💚	💚	🐭 Tiny Matrix	➖
🧊 kettle-dev/kettle-family on CodeBerg	An Ethical Mirror (Donate)	💚	💚	➖	⭕️ No Matrix	➖
🐙 kettle-dev/kettle-family on GitHub	Another Mirror	💚	💚	💚	💯 Full Matrix	💚
🎮️ Discord Server		Let's	talk	about	this	library!

Available as part of the Tidelift Subscription.

Install the gem and add to the application's Gemfile by executing:

bundle add kettle-family

If bundler is not being used to manage dependencies, install the gem by executing:

gem install kettle-family

kettle-family reads .kettle-family.yml from the family root by default. Use --config PATH to load a different file.

For a flat repository that releases from multiple long-lived branches, list the release branches under release.target_branches. The branch list is processed in order. Each branch must be clean enough for git checkout, and each branch is treated as a normal flat gem after checkout.

release:
  target_branches:
    - r1_8-even-v0
    - r1_9-even-v2
    - r2_0-even-v4

Publish runs use bundle exec kettle-release by default, which means full publish flows inherit the kettle-pre-release gate from kettle-release. The release command can be overridden when a family needs a custom wrapper:

release:
  publish_command: bundle exec kettle-release

Resume and security-release options pass through to kettle-release. Passing --start-step N appends start_step=N; as with direct kettle-release usage, N > 1 resumes after the pre-release gate and should be used only after that gate already passed or the failure was intentionally handled:

kettle-family release --publish --start-step 10 --local-ci

Executed publish runs skip versions that are already published. CI failures abort by default; pass --continue-ci-failures to set K_RELEASE_CI_CONTINUE=true for the underlying kettle-release process.

Inspect discovery and release plans before executing them:

kettle-family discover
kettle-family release

Run release prep/build phases without publishing:

kettle-family release --execute

Publish through kettle-release. A full publish first runs the kettle-pre-release gate, then prompts once for the gem signing key password and leaves RubyGems MFA prompts interactive:

kettle-family release --publish --execute

Resume a failed family publish after fixing the failure. Already published versions are skipped automatically; start_step is passed to kettle-release for unreleased members that still need work. Use --start-step only after the pre-release gate already passed or the failure was intentionally handled:

kettle-family release --publish --execute --start-step 10

For security updates, publish locally before pushing commits/tags to remotes by passing --local-ci through to kettle-release:

kettle-family release --publish --execute --local-ci

If you intentionally need to continue after CI failures, opt in explicitly:

kettle-family release --publish --execute --continue-ci-failures

While kettle-dev tools are free software and will always be, the project would benefit immensely from some funding. Raising a monthly budget of... "dollars" would make the project more sustainable.

We welcome both individual and corporate sponsors! We also offer a wide array of funding channels to account for your preferences. Currently, Open Collective is our preferred funding platform.

If you're working in a company that's making significant use of kettle-dev tools we'd appreciate it if you suggest to your company to become a kettle-dev sponsor.

You can support the development of kettle-dev tools via GitHub Sponsors, Liberapay, PayPal, Open Collective and Tidelift.

Support us with a monthly donation and help us continue our activities. [Become a backer]

NOTE: kettle-readme-backers updates this list every day, automatically.

No backers yet. Be the first!

Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]

NOTE: kettle-readme-backers updates this list every day, automatically.

No sponsors yet. Be the first!

I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small. Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions. I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).

If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in bundle fund.

I’m developing a new library, floss_funding, designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.

Floss-Funding.dev: 👉️ No network calls. 👉️ No tracking. 👉️ No oversight. 👉️ Minimal crypto hashing. 💡 Easily disabled nags

See SECURITY.md.

If you need some ideas of where to help, you could work on adding more code coverage, or if it is already 💯 (see below) check issues or PRs, or use the gem and think about how it could be better.

We so if you make changes, remember to update it.

See CONTRIBUTING.md for more detailed instructions.

See CONTRIBUTING.md.

Everyone interacting with this project's codebases, issue trackers, chat rooms and mailing lists agrees to follow the .

Made with contributors-img.

Also see GitLab Contributors: https://gitlab.com/kettle-dev/kettle-family/-/graphs/main

⭐️ Star History

This library follows for its public API where practical. For most applications, prefer the Pessimistic Version Constraint with two digits of precision.

For example:

spec.add_dependency("kettle-family", "~> 0.0")

See CHANGELOG.md for a list of releases.

The gem is available as open source under the terms of the MIT .

See LICENSE.md for the official copyright notice.

Maintainers have teeth and need to pay their dentists. After getting laid off in an RIF in March, and encountering difficulty finding a new one, I began spending most of my time building open source tools. I'm hoping to be able to pay for my kids' health insurance this month, so if you value the work I am doing, I need your support. Please consider sponsoring me or the project.

To join the community or get help 👇️ Join the Discord.

To say "thanks!" ☝️ Join the Discord or 👇️ send money.

💌 💌 💌

Many parts of this project are actively managed by a kettle-jem smart template utilizing StructuredMerge.org merge contracts.

Thanks for RTFM. ☺️