Release: drain PR queue, fix release tagging, promote Dev_new_gui → main #11825

Activity

1. mrveiss

   added

   priority: high

   infrastructure

   ci

   umbrellaEpic/umbrella tracking issue grouping member issuesEpic/umbrella tracking issue grouping member issues

   on Jul 17, 2026
2. mrveiss commented on Jul 17, 2026

   

   mrveiss

   on Jul 17, 2026

   OwnerAuthor

   More actions

   Progress 09:35Z

   Task 1 (drain queue): #11822, #11803 + dependabot #11818/#11817/#11816/#11811/#11809/#11808 merged (partly by parallel session). Remaining open: #11824, #11819 (CI running, no failures), #11827 (recreated openai bump, CI running), #11800 (dependabot-orphaned — branch updated manually via API; coverage gap filed as #11829).

   Task 2 (release.yml fix): PR #11828 open, CI running. Guard simulated: any cliff bump ≤ v0.5.0 → releases v0.5.1.

   Next: merge remaining PRs when green → legacy-tag surgery (v0.4.1/v0.5.0 → their main-side parents) → promotion PR → verify release.
3. mrveiss

   added a commit that references this issue on Jul 17, 2026

   Merge pull request #11842 from mrveiss/Dev_new_gui

   ...

   72fcafe
4. mrveiss commented on Jul 17, 2026

   

   mrveiss

   on Jul 17, 2026

   OwnerAuthor

   More actions

   Session paused — checkpoint

   Release v0.5.1 is published and correct: tag → promotion merge 72fcafe (ancestor of main ✓), notes cover the promoted range. PR queue drained to 0; changelog landed on main (#11851); back-merge #11852 (-s ours) absorbed main into Dev_new_gui (0 behind).

   Discovered along the way (2 latent release-automation bugs)

   • release.yml: changelog-PR step fails every release — missing pull-requests: write permission (GITHUB_TOKEN can't createPullRequest) #11853 — release.yml lacks pull-requests: write; changelog-PR step has failed every release.
   • release.yml self-triggers on its own changelog commit → spurious release (latent infinite loop once #11853 lands) #11855 — release.yml self-triggers on its own changelog commit → git-cliff patch-bumps → spurious v0.5.2 published. Would be an infinite loop once release.yml: changelog-PR step fails every release — missing pull-requests: write permission (GITHUB_TOKEN can't createPullRequest) #11853 is fixed.

   Safe-state note

   Both fixes sit in PR #11854 (paths-ignore guard + permission), NOT yet merged. Leaving it unmerged is the safe state: the permission bug currently blocks the loop. Do NOT merge #11854 until reviewed — but when merged, both fixes land together (guard prevents the loop).

   One decision pending (destructive → needs owner)

   Spurious v0.5.2 (tag+release at changelog commit 0afb93b). Delete it (clean history; v0.5.1 remains the release) or keep it (harmless, becomes current). Awaiting owner.

   Remaining on resume

   Decide v0.5.2 → merge #11854 → close #11826/#11853/#11855/#11829 + umbrella #11825 → remove worktrees (issue-11826, backmerge-v0.5.1) + branches.
5. mrveiss commented on Jul 17, 2026

   

   mrveiss

   on Jul 17, 2026

   OwnerAuthor

   More actions

   Update — v0.5.2 deleted (owner-approved)

   Spurious v0.5.2 release + remote tag deleted. v0.5.1 is the clean, sole release for this promotion.

   Remaining on resume (nothing time-sensitive; safe as-is)

   1. Review + merge PR fix(release): grant pull-requests:write so changelog PR step succeeds (#11853) #11854 (release.yml: pull-requests: write + paths-ignore self-trigger guard — the two fixes must land together).
   2. Close release.yml tags the squashed-away changelog commit — release tags never land on main; versions regress (v0.5.0→v0.4.1), wrong notes, silent-skip risk #11826 / release.yml: changelog-PR step fails every release — missing pull-requests: write permission (GITHUB_TOKEN can't createPullRequest) #11853 / release.yml self-triggers on its own changelog commit → spurious release (latent infinite loop once #11853 lands) #11855 / dependabot.yml: no uv ecosystem entry — knowledge-base-mcp/uv.lock unmanaged, orphaned PR #11800 can't rebase #11829 and umbrella Release: drain PR queue, fix release tagging, promote Dev_new_gui → main #11825.
   3. Remove worktrees issue-11826 + backmerge-v0.5.1 and their local branches.

   Session paused before doing the above.
6. mrveiss commented on Jul 18, 2026

   

   mrveiss

   on Jul 18, 2026

   OwnerAuthor

   More actions

   ✅ Release complete — v0.5.1

   All tasks done.

   Task	Status
   1. Drain PR queue	✅ fixes #11824/#11819/#11822/#11803, all dependabot, test-rot #11841 merged; #11800 orphan handled
   2. Fix release tagging	✅ #11828 (GITHUB_SHA + monotonic guard) + legacy tag surgery
   3. Promote Dev_new_gui → main	✅ #11842 (--merge --admin)
   4. Verify release	✅ v0.5.1 tag on promotion merge (ancestor of main), notes = correct range

   Discovered + fixed along the way

   • release.yml tags the squashed-away changelog commit — release tags never land on main; versions regress (v0.5.0→v0.4.1), wrong notes, silent-skip risk #11826 (tag lineage) — fixed fix(release): tag the pushed main SHA + monotonic version guard (#11826) #11828 ✅
   • release.yml: changelog-PR step fails every release — missing pull-requests: write permission (GITHUB_TOKEN can't createPullRequest) #11853 (missing pull-requests: write) — fixed fix(release): grant pull-requests:write so changelog PR step succeeds (#11853) #11854 ✅
   • release.yml self-triggers on its own changelog commit → spurious release (latent infinite loop once #11853 lands) #11855 (self-trigger loop → spurious v0.5.2) — fixed fix(release): grant pull-requests:write so changelog PR step succeeds (#11853) #11854 ✅; spurious v0.5.2 deleted
   • dependabot.yml: no uv ecosystem entry — knowledge-base-mcp/uv.lock unmanaged, orphaned PR #11800 can't rebase #11829 (dependabot uv coverage gap) — OPEN, low-priority follow-up

   Post-release housekeeping

   • Changelog chore(release): changelog for v0.5.1 #11851 on main; back-merge merge(main): absorb v0.5.1 promotion + changelog into Dev_new_gui (-s ours) #11852 (-s ours) — main absorbed into Dev_new_gui
   • fix(release): grant pull-requests:write so changelog PR step succeeds (#11853) #11854 fixes (permission + paths-ignore) live on Dev_new_gui; activate at next promotion

   Closing umbrella. Only #11829 remains as an independent follow-up.
7. mrveiss

   closed this as completedon Jul 18, 2026
8. mrveiss commented on Jul 18, 2026

   

   mrveiss

   on Jul 18, 2026

   OwnerAuthor

   More actions

   Open follow-ups from this release (independent, tracked separately):

   • dependabot.yml: no uv ecosystem entry — knowledge-base-mcp/uv.lock unmanaged, orphaned PR #11800 can't rebase #11829 — dependabot missing uv ecosystem entry (priority: low)
   • release.yml: monotonic guard rewrites version but notes step still uses git-cliff --latest range (inert unless guard fires) #11861 — monotonic-guard vs notes-range inconsistency, inert unless the guard fires (priority: low)

   Review pass confirms: 0 open PRs; my worktrees/branches removed; core fix (tag GITHUB_SHA) is the root-cause fix with the guard as inert defense-in-depth (no regression on normal releases); the dual-sandbox-validator duplication adjacent to fix #11824 was already consolidated by #11846 (shared resolve_within_sandbox, #11844).