v1.2.14

1.2.14 - 2026-07-31

• TAG: v1.2.14
• COVERAGE: 94.22% -- 4175/4431 lines in 28 files
• BRANCH COVERAGE: 76.69% -- 1622/2115 branches in 28 files
• 28.88% documented

Added

• Release publish/build commands now write per-member transcript logs under
  tmp/kettle-family/release-*, and failure summaries include the log path.

• Release progress now renders child kettle-release remote_parity events,
  keeping remote fetch, skip, failure, and completion activity visible without
  scraping raw command output.

• Release progress now renders child kettle-release ci_monitor events with
  provider and workflow or pipeline context, so CI activity is visible as
  structured progress.

• Release progress now renders child kettle-release pre_release events, so
  pre-release checks are visible as structured progress while raw output stays
  in the transcript log.

• Release progress now renders child kettle-changelog changelog events, so
  release plan, coverage, and changelog update activity is visible as structured
  progress.

Changed

• Family release now keeps raw child kettle-release output in the per-member
  transcript log by default and renders structured NDJSON progress in the
  terminal, with raw passthrough still available under verbose/debug output.
• Release summary footers now include the transcript log directory when release
  logs were written, including successful runs where raw output stayed quiet.
• Release progress now renders child command_step summaries, so phases can
  show context such as release:bundle_lock:Gemfile or
  release:yard:documentation.
• Release progress now renders child release_lockfile and release_probe
  events, so lockfile reset retries and published-gem availability probes show
  as structured progress.
• Release progress now renders GitHub CI wait/start/tick events with completion
  counts, so CI monitoring no longer appears stuck while waiting for workflows.
• Release preflight now renders through the shared progress event tape instead
  of printing separate start and finish lines for each successful phase.

Fixed

• Release preflight no longer prints a nested 1Password authorization alert
  between the phase start and finish lines; the preflight phase itself is the
  user-facing authorization notice.

• Family release runs can now pass configured required release remotes through
  to kettle-release, allowing mirrors to remain optional while primary remotes
  still block release parity failures.

Community support 👉️

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