v1.0.1

1.0.1 - 2026-07-20

• TAG: v1.0.1
• COVERAGE: 95.44% -- 2534/2655 lines in 23 files
• BRANCH COVERAGE: 77.89% -- 877/1126 branches in 23 files
• 29.10% documented

Added

• kettle-family release-state now includes an ahead column counting commits
  from the latest release tag to the local default branch when available.

• kettle-family release now accepts --skip-remotes and forwards the
  comma-separated remote skip list to member kettle-release runs.

• kettle-family --only now accepts release-state tokens unreleased,
  prepared, and pending; multiple tokens are combined with logical AND.

• kettle-family template now accepts --verbose and forwards verbose mode to
  member kettle-jem runs instead of forcing quiet JSON output.

• kettle-family template now runs kettle-jem prepare before full templating
  for Kettle Jem-powered members so templating-only dependency bootstraps, such
  as parser packages, are available before the full template command loads.

• kettle-family template now uses kettle-jem --events as its default
  templating interface, including verbose and single-job runs, and streams
  newline-delimited JSON template phase, recipe, post-apply, command-step,
  diagnostic, and summary events as member-prefixed progress lines.

Deprecated

• kettle-family bump-version is now deprecated in favor of kettle-family bump.

Fixed

• The templating prepare phase now disables only the implicit family local path
  environment variable unless it was explicitly provided, avoiding stale local
  Gemfile activation failures before the prepare payload can refresh generated
  modular Gemfiles.

• The templating prepare phase now runs outside each member's Bundler context so
  it can repair stale generated Gemfiles before Bundler evaluates them.

• kettle-family template preparation now handles custom non-kettle-jem
  template commands without treating no-op dependency preparation as failure.

• kettle-family release-state now counts ahead from the release tag to the
  checked-out member HEAD.

• Generated docs now retain the YARD _index.html content wrapper after
  regeneration with the shared YARD postprocessing stack.

Official Discord 👉️

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