fix: release only on user request after changes merge #306

Merged

erik merged 3 commits from fix/task-8e7134b9-explicit-release-lifecycle into main

2026-10-26 15:28:01 -05:00

erik commented

2026-10-26 15:09:12 -05:00

Owner

Corrected lifecycle (developer-approved)

Normal task changes pass checks/review, receive human approval, and merge to main. No release-skill/changelog requirement or automatic publication.
Only when the user explicitly requests a release, the agent evaluates merged changes, chooses versions, and prepares a release branch containing the changelog/version updates.
Explicit release.yml dispatch validates the exact branch/commit, finishes checks and artifact publication/verification, then installs/runs the pinned Slug CLI to post the changelog note.

Changes

Restore non-publishing PR/main CI; remove per-merge changelog gates.
General release skill/dispatcher now follows explicit user-requested release-branch preparation.
Commit the source range base for deterministic historical links. Completion records retain release branch/tag provenance without auto-merging main.
Recover the original reviewed source even after human-approved non-fast-forward integration; preserve artifact integrity, contract archive handling, private publisher configuration, and safe retries.
Update contributor/operator documentation.

Verification

./scripts/pre-pr.sh passed all checks and 1,336 local tests, including integration coverage.
Forgejo CI #537 passed for a67bf222c4.
Independent full re-review found no actionable defects after the source-recovery fix; final follow-up review approved the documentation cleanup at current head.
Tests cover no publication from normal CI, dispatch-only releases, exact release branches/source ranges, real dispatcher dry-run, non-fast-forward release integration, long commit history/body handling, and artifact completion before CLI installation/announcement.
CI retains test:ci only. No integration/browser/container testing was added.
No release was dispatched and no new feed note was published during this rework. Old per-merge announcement recovery remains paused/superseded.

Gates

Explicit human merge approval required.
Merging this PR must not trigger a release. Publishing waits for a separate user release request.

Task: #task-8e7134b9

## Corrected lifecycle (developer-approved) 1. Normal task changes pass checks/review, receive human approval, and merge to main. No release-skill/changelog requirement or automatic publication. 2. Only when the user explicitly requests a release, the agent evaluates merged changes, chooses versions, and prepares a release branch containing the changelog/version updates. 3. Explicit release.yml dispatch validates the exact branch/commit, finishes checks and artifact publication/verification, then installs/runs the pinned Slug CLI to post the changelog note. ## Changes - Restore non-publishing PR/main CI; remove per-merge changelog gates. - General release skill/dispatcher now follows explicit user-requested release-branch preparation. - Commit the source range base for deterministic historical links. Completion records retain release branch/tag provenance without auto-merging main. - Recover the original reviewed source even after human-approved non-fast-forward integration; preserve artifact integrity, contract archive handling, private publisher configuration, and safe retries. - Update contributor/operator documentation. ## Verification - ./scripts/pre-pr.sh passed all checks and 1,336 local tests, including integration coverage. - Forgejo CI #537 passed for a67bf222c4041749ec7cf22b987bddf8f776edb3. - Independent full re-review found no actionable defects after the source-recovery fix; final follow-up review approved the documentation cleanup at current head. - Tests cover no publication from normal CI, dispatch-only releases, exact release branches/source ranges, real dispatcher dry-run, non-fast-forward release integration, long commit history/body handling, and artifact completion before CLI installation/announcement. - CI retains test:ci only. No integration/browser/container testing was added. - No release was dispatched and no new feed note was published during this rework. Old per-merge announcement recovery remains paused/superseded. ## Gates - Explicit human merge approval required. - Merging this PR must not trigger a release. Publishing waits for a separate user release request. Task: #task-8e7134b9

Rows
Columns