Skip to content

chore(sync): merge main into next after hotfix #572 (#571) - #573

Merged
ss-o merged 8 commits into
nextfrom
feature-571-sync-main
Sep 27, 2026
Merged

ss-o merged 8 commits into
nextfrom
feature-571-sync-main

Conversation

@ss-o

@ss-o ss-o commented Sep 27, 2026

Copy link
Copy Markdown
Member

Description

Synchronize hotfix #572 from main into next, as the branch model requires before ordinary development continues (z-shell/.github runbooks/branch-protection.md, "Hotfix synchronization").

The branch starts at next (7d9feb8) and adds one signed merge commit of main (4f2c0a7). The merge was clean: the diff against next is exactly the five files from #572, and it also brings the earlier promotion merge commits on main into next's ancestry, which is expected.

Merge this with a merge commit so the synchronization merge is preserved. After merge, git merge-base --is-ancestor origin/main origin/next must succeed.

Related issues

Refs #571

Type of change

  • fix - bug fix (non-breaking)
  • feat - new feature (non-breaking)
  • feat! / fix! - breaking change
  • perf - performance improvement
  • refactor - code change with no functional impact
  • docs - documentation only
  • test - test addition or correction
  • build - build system or dependency change
  • ci - CI/workflow change
  • style - formatting with no behavior change
  • chore - maintenance / dependency bump
  • revert - revert of an earlier change

Checklist

  • Ordinary work targets next; only same-repository hotfixes target main
  • A next to main promotion uses a merge commit and records both parent SHAs (not a promotion)
  • Commit messages follow Conventional Commits format
  • Any Co-authored-by trailer credits a real human, never a bot, AI agent, or automation
  • I have read the contribution guidelines
  • Existing tests pass (zsh -n zi.zsh / Trunk checks)
  • Documentation updated if needed

Verification

ss-o added 8 commits September 3, 2026 01:17
Promotes the reviewed next candidate with preserved ancestry.
Promotes the reviewed next candidate with preserved ancestry.
Promotes the reviewed next candidate with preserved ancestry.
Promotes the reviewed next candidate with preserved ancestry.
Promotes the reviewed next candidate with preserved ancestry.
Dependabot security updates always target the default branch, so the
main source guard rejected every one of them. Move the decision into
scripts/main-branch-guard.zsh and also allow a same-repository
dependabot/* branch whose pull-request author is dependabot[bot].

The workflow checks out only that script from the base branch, so it
never runs pull-request code, and needs contents: read for that. The
new Main Branch Guard job runs tests/main-branch-guard.zsh.

@ss-o ss-o left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self-review of head 6abfbab.

No findings. The branch is next at 7d9feb8 plus one signed merge of main at 4f2c0a7, with no conflict resolution. git diff origin/next HEAD is exactly the five files of #572, byte for byte what main carries. tests/main-branch-guard.zsh passes on this head.

This must merge with a merge commit, not squash, so main becomes an ancestor of next; check git merge-base --is-ancestor origin/main origin/next afterwards.

@ss-o
ss-o merged commit 357d9b1 into next Sep 27, 2026
131 checks passed
@ss-o
ss-o deleted the feature-571-sync-main branch September 27, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant