Skip to content

Releases: kettle-dev/kettle-family

v0.1.0

10 Jun 08:41
v0.1.0
9e7c316

Choose a tag to compare

0.1.0 - 2026-06-10

  • TAG: v0.1.0
  • COVERAGE: 94.28% -- 742/787 lines in 17 files
  • BRANCH COVERAGE: 78.25% -- 223/285 branches in 17 files
  • 42.34% documented

Added

  • Added the initial kettle-family CLI discovery slice with config loading, gemspec discovery, dependency ordering, selection, and JSON reports.
  • Added workflow command planning/execution, readiness checks, and failure resume hints for check, test, lint, and docs.
  • Added the template workflow with kettle-jem command planning, template environment, lockfile normalization hooks, and explicit family commit safety.
  • Added bump-version VERSION with Prism-backed version constant edits, exact family dependency pin updates, and check/dry-run/execute modes.
  • Added the release workflow with readiness/changelog gates, build-only and publish modes, fixed-order planning, and explicit tag/push phases.
  • Added sibling-repository discovery, branch lane mappings, and a read-only branch-lanes audit command for multi-branch release planning.
  • Added release.target_branches config so a flat repository can release sequentially across configured branch targets.
  • Added kettle-family release passthroughs for kettle-release resume/security options and automatic already-published skips for resumable family releases.
  • Added explicit runtime dependency wiring for extracted stdlib gems used by the CLI.

Fixed

  • Updated generated project metadata links to use the migrated kettle-dev
    GitHub organization.
  • Restored docs/CNAME so the generated documentation site keeps its custom domain.
  • Corrected misspelled contact metadata to use galtzo.com.
  • Fixed CI load failures on engines without compatible pty support by falling back to Open3 for interactive release commands.
  • Fixed Ruby 3.2 version-bump support by loading Prism lazily and wiring the Prism gem only for MRI versions that need it.

Official Discord πŸ‘‰οΈ Live Chat on Discord

Many paths lead to being a sponsor or a backer of this project. Are you on such a path?

OpenCollective Backers OpenCollective Sponsors Sponsor Me on Github Liberapay Goal Progress Donate on PayPal

Buy me a coffee Donate on Polar Donate to my FLOSS efforts at ko-fi.com Donate to my FLOSS efforts using Patreon