fix(stack): publish ahead parents safely and support older gh - #45
Merged
kitlangton merged 1 commit intoAug 28, 2026
Merged
Conversation
Copy link
Copy Markdown
Owner
Sorry, something went wrong.
Journal remote-only parent publications independently from local branch backups, use explicit push leases, and retain cumulative recovery checkpoints across keep-going stacks. Read GitHub PR details through REST rather than version-dependent gh pr view fields. Add real-Git regression coverage and patch changesets.
This was referenced Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
After editing a stack parent locally, stack sync --apply can repair and publish its child while leaving the remote parent at the old commit. Separately, older GitHub CLI versions omit headRepository.nameWithOwner, causing sync to reject valid PR JSON.
What Changes
Bare sync remains a non-mutating preview. Publication is scoped to the selected stack, includes parents with remote-only children, and refuses diverged or unknown remote tips. Explicit expected-tip leases guard new parent-publication pushes; these pushes do not implicitly publish tags.
Undo Boundaries
A remote-only publication must not be undone by resetting the local parent. The journal therefore records each destination's before/after tips separately from local branch backups. For example, a parent that started at local A2 / remote A1 returns to that exact split after undo.
Checkpoints precede publication and retain earlier stacks' recovery data during keep-going runs. Undo handles partial publication and partial rollback, but refuses unexpected remote tips. Journals containing remote updates use version 2 so older CLIs reject rather than ignore them; version 1 journals remain readable.
Scope
Independent fixes for the behaviors reported in #21 and #41, with regression tests, documentation, and patch changesets. Request-concurrency work in #43 and CI repository settings are not changed.
Verification
GIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_SYSTEM=/dev/null bun run test bun run typecheck bun run format:check bun run lint bun run package:smoke bun run changeset:status --since origin/main bun src/cli.ts --help bun src/cli.ts sync --help bun src/cli.ts undo --help git diff --check163 tests pass, with no skipped or expected-failure regressions. Real-Git fixtures cover fork/origin tips, missing refs, stale leases, scoped previews, checkpoint failures, partial publication/undo, keep-going recovery, and tag suppression. The GitHub detail adapter was also smoke-tested with a read-only lookup of #41.