Skip to content

Promote 0.57.4: keep teardown in the current session - #413

Merged
github-actions[bot] merged 4 commits into
mainfrom
dev
Nov 6, 2026
Merged

github-actions[bot] merged 4 commits into
mainfrom
dev

Conversation

@ac8318740

@ac8318740 ac8318740 commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

Summary

Promote 0.57.4 to main. Worktree teardown stays in the current session and requires verified relocation before removing its checkout.

PR #412 merges the teardown fix into dev. PR #414 fixes the promotion blocker by running version validation on every label event. Dev is at 51eff01.

Both feature PRs pass all five CI checks. Independent reviews find no remaining blockers.

How it works

flowchart LR
    A[Approve teardown plan] --> B[Attempt supported same-session relocation]
    B --> C{Verify harness cwd and pane move}
    C -->|Pass| D[Remove eligible worktrees]
    C -->|Blocked| E[Keep current checkout and branches]
Loading

The promote-to-main label triggers the repository's guarded fast-forward workflow after the promotion checks pass.

What changed

  • Authorize moving the current session through removal-plan approval
  • Remove replacement-session, fork, and handoff fallbacks
  • Preserve other Herdr panes and the current Orca checkout
  • Bump plugin, root, and CLI package versions to 0.57.4
  • Run version validation on label changes instead of creating a skipped required check

Blast radius

  • Changes teardown guidance for Herdr, Orca, and sessions without a host pane
  • Preserves repository-wide scanning, approval, branch checks, and data-loss protections
  • Adds no runtime cwd capability; live Pi relocation remains unverified
  • Changes no plugin runtime logic or dependencies
  • Runs the unchanged version validator on every configured PR label event; preserves branch protection

Test plan

  • Independent instruction review, Markdown checks, skill line cap, and prose lint
  • Local build, generated-output checks, lint, typecheck, and version gate
  • All five checks pass on the feature PR
  • Updated promotion PR: CLI, shell suites, plugin wiring, Pi extension, tests, and version gate
  • Inspect promotion review comments before relabeling (none; no AI review workflow configured)
  • Guarded fast-forward succeeds; main, dev, and v0.57.4 resolve to 51eff014274bbf0e8b6f1cf004ff61b51f5ecd41
  • Tag workflow stages acstack@0.57.4 for npm approval

No live teardown runs for this instruction-only change. A session keeps its checkout if it cannot verify relocation.

Authorize moving the current session after plan approval.
Remove replacement-session fallbacks and preserve other live panes.
Bump the plugin to 0.57.4.
Keep worktree teardown in the current session
@ac8318740 ac8318740 added promote-to-main Fast-forward main to dev. Adding this runs .github/workflows/promote.yml. and removed promote-to-main Fast-forward main to dev. Adding this runs .github/workflows/promote.yml. labels Nov 6, 2026
Run the version gate instead of creating a skipped check that can
supersede the passing result required by branch protection.
Add regression checks for label triggers and unconditional validation.
Run version validation when promotion labels change
@ac8318740 ac8318740 added the promote-to-main Fast-forward main to dev. Adding this runs .github/workflows/promote.yml. label Nov 6, 2026
@github-actions
github-actions Bot merged commit 51eff01 into main Nov 6, 2026
13 checks passed
@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

Promoted. main fast-forwarded to dev at 51eff014274bbf0e8b6f1cf004ff61b51f5ecd41.

The tag-release workflow was dispatched. Watch its own run for the vX.Y.Z tag.

No merge commit, so main stays an ancestor of dev and the next promotion fast-forwards too. No back-merge into dev is needed.

Workflow run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

promote-to-main Fast-forward main to dev. Adding this runs .github/workflows/promote.yml.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant