v1.2.13
1.2.13 - 2026-07-31
- TAG: v1.2.13
- COVERAGE: 94.09% -- 4043/4297 lines in 28 files
- BRANCH COVERAGE: 76.48% -- 1538/2011 branches in 28 files
- 28.84% documented
Fixed
-
Family publish runs now keep release secrets provider interaction in
kettle-familyby default, so--secrets-providerno longer gets passed down
to childkettle-releasecommands unless the configured publish command
explicitly includes it. -
Family release progress now renders child
kettle-releasesecret_provider
events, keeping keepalive and prompt-response activity visible when a release
command emits NDJSON. -
kettle-family statenow querieskettle-jemtransfer changelog totals
outside the active bundle when the root bundle does not includekettle-jem,
so the transfer lag column header can show the real total instead ofT(?). -
kettle-familylocal development bundles now localizekettle-dev's direct
sibling runtime dependencies whenKETTLE_DEV_DEVis enabled, so unreleased
floors such askettle-ndjson >= 0.1.4resolve during family development. -
Release dry-runs now stop after planned lockfile normalization when a member
has local path remotes, avoiding a false readiness failure on lockfiles that
would be normalized under--execute. -
Release state now reads kettle-jem transfer changelog replay cursors from
.structuredmerge/kettle-jem.lock, soT(n)reports actual lag instead of
treating every member as missing all transfer changelogs. -
kettle-family statenow labels the transfer changelog column asT(n),
wherenis the total transfer changelog count and row values are the lag
after each member's stored replay cursor. -
kettle-family statenow uses an ASCII^ / vahead/behind column header so
terminal table alignment is stable in monospace output. -
Text reports now repeat the command context in the final summary footer so the
command, family, mode, config, order, and release target details remain visible
after long runs. -
Failed streamed release commands now report the last useful output line when
no explicit failure marker is present, avoiding emptyoutput omitted
summaries for Bundler boot failures. -
Template execution now aligns stale managed
nomonoGemfile floors and
lockfiles before member bundles run, avoiding already-activatednomono
conflicts during family templating. -
kettle-familynow loadskettle-devthrough its public entrypoint instead
of direct nested implementation files. -
Command summaries now include total elapsed wall time in the final footer.
-
Parent-owned RubyGems MFA lookup failures during release now fall back to
manual OTP entry when possible, and otherwise fail the member cleanly instead
of escaping from a worker thread with a misleading release summary. -
Dependency-floor CI bundle validation now recognizes workflow
env: BUNDLE_GEMFILEentries, including${{ github.workspace }}paths, so
release waves wait for just-published floors before pushing dependent CI
workflows that install through setup-ruby-flash.
Many paths lead to being a sponsor or a backer of this project. Are you on such a path?