kettle-dev / kettle-dev / 39859749575

86%

Build Type

push

github

Committed by pboling

Commit Message

🐛 Keep publish-boundary lockfile drift local in detached checkout topologies

revalidate_publish_lockfile_changes! (added in 3.1.22) ran
ensure_trunk_synced_before_push! + push! + monitor_workflows_after_push!
whenever publish-time lockfile normalization detected drift. Family
member publishes run in a detached worktree the family orchestrator owns
end-to-end, so push! died on 'git push origin HEAD' (silently — both
retries only warn) and the CI re-trigger then aborted the wave trying to
open a validation PR for a literal HEAD ref. A bare detached HEAD hits
the same meaningless path.

The publish-boundary contract for those topologies: drift stays local to
the checkout (the built gem does not embed the development lockfile; the
family validated the pushed HEAD), and branch operations are skipped
entirely.

Specs cover family member publish mode (no commit/push/CI, build still
materializes the updated snapshot) and bare detached HEAD. Regression
context: https://github.com/kettle-dev/kettle-dev/issues/52

Coverage Stats

2231 of 2952 branches covered (75.58%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

19 existing lines in 4 files now uncovered.

5807 of 6333 relevant lines covered (91.69%)

62.24 hits per line