KofTwentyTwo/gclo
2
0 Fork 0
Code Issues 28 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

Rehearse the gated release chain with v1.0.1-beta.1 #55

New Issue
Closed
opened 2026-10-09 11:21:37 +00:00 by KofTwentyTwo · 1 comment
KofTwentyTwo commented 2026-10-09 11:21:37 +00:00 (Migrated from github.com)
Copy link
Copy source

Context

#44 rebuilt the release workflow into three gated jobs (verify → gates via workflow_call → release). The chain has never executed end to end; the first v* tag after PR #51 merges is its first real run.

Task

  • After #51 merges, tag v1.0.1-beta.1 on the main merge commit and push it (dev channel; stable users are unaffected).
  • Confirm each stage: verify (tag accepted, ancestry check passes), gates (CI workflow called with ui-tests-advisory: true), release (draft created, assets attached, changelog generated, published; immutable).
  • Confirm the resulting release is marked prerelease on channel dev with gclo-dev-Setup.exe, portable zip, full nupkg, CLI zip and releases.dev.json.
  • If any stage fails: fix forward on main and cut v1.0.1-beta.2; never reuse the tag (immutable releases + tag ruleset).
  • Record the outcome here and in docs/RELEASING.md if anything in the runbook turned out wrong.

Related: #44, #55 (self-update verification on the new Velopack).

## Context #44 rebuilt the release workflow into three gated jobs (`verify` → `gates` via `workflow_call` → `release`). The chain has never executed end to end; the first `v*` tag after PR #51 merges is its first real run. ## Task - [ ] After #51 merges, tag `v1.0.1-beta.1` on the `main` merge commit and push it (dev channel; stable users are unaffected). - [ ] Confirm each stage: verify (tag accepted, ancestry check passes), gates (CI workflow called with `ui-tests-advisory: true`), release (draft created, assets attached, changelog generated, published; immutable). - [ ] Confirm the resulting release is marked prerelease on channel `dev` with `gclo-dev-Setup.exe`, portable zip, full nupkg, CLI zip and `releases.dev.json`. - [ ] If any stage fails: fix forward on `main` and cut `v1.0.1-beta.2`; never reuse the tag (immutable releases + tag ruleset). - [ ] Record the outcome here and in `docs/RELEASING.md` if anything in the runbook turned out wrong. Related: #44, #55 (self-update verification on the new Velopack).
KofTwentyTwo commented 2026-10-09 14:02:40 +00:00 (Migrated from github.com)
Copy link
Copy source

Rehearsal outcome — v1.0.1-beta.1 (2026-10-09)

Tagged on main merge commit 187ac3e (PR #59) and pushed. Release run 37940343634: success, end to end on the first attempt.

Stage Result
verify tag accepted, ancestry check passed, version 1.0.1-beta.1, prerelease → channel dev
gates (ci.yml via workflow_call) Build and test (x64) ✅ · Format ✅ · UI end-to-end tests ✅ (advisory, but it passed — including the new TableView fixture tests)
release publish CLI, Velopack pack (delta baseline downloaded from v1.0.0), SHA256SUMS.txt written, provenance attested, draft created, CLI zip + checksums attached, changelog generated, published

Result: https://github.com/KofTwentyTwo/gclo/releases/tag/v1.0.1-beta.1 — prerelease, not draft, immutable. Assets: gclo-dev-Setup.exe, gclo-dev-Portable.zip, gclo-1.0.1-beta.1-dev-full.nupkg, gclo-1.0.1-beta.1-dev-delta.nupkg, gclo-cli-win-x64.zip, releases.dev.json, SHA256SUMS.txt.

Skipped by design: NuGet push, winget, Scoop/Chocolatey (prerelease; and the secrets are unset — #7). Nothing in docs/RELEASING.md turned out wrong. Closing; #56 (self-update on the dev channel) can now be verified against this release.

## Rehearsal outcome — `v1.0.1-beta.1` (2026-10-09) Tagged on `main` merge commit 187ac3e (PR #59) and pushed. Release run [37940343634](https://github.com/KofTwentyTwo/gclo/actions/runs/37940343634): **success**, end to end on the first attempt. | Stage | Result | |---|---| | verify | tag accepted, ancestry check passed, version `1.0.1-beta.1`, prerelease → channel `dev` | | gates (ci.yml via `workflow_call`) | Build and test (x64) ✅ · Format ✅ · UI end-to-end tests ✅ (advisory, but it passed — including the new TableView fixture tests) | | release | publish CLI, Velopack pack (delta baseline downloaded from v1.0.0), `SHA256SUMS.txt` written, provenance attested, draft created, CLI zip + checksums attached, changelog generated, published | Result: https://github.com/KofTwentyTwo/gclo/releases/tag/v1.0.1-beta.1 — **prerelease**, not draft, immutable. Assets: `gclo-dev-Setup.exe`, `gclo-dev-Portable.zip`, `gclo-1.0.1-beta.1-dev-full.nupkg`, `gclo-1.0.1-beta.1-dev-delta.nupkg`, `gclo-cli-win-x64.zip`, `releases.dev.json`, `SHA256SUMS.txt`. Skipped by design: NuGet push, winget, Scoop/Chocolatey (prerelease; and the secrets are unset — #7). Nothing in `docs/RELEASING.md` turned out wrong. Closing; #56 (self-update on the dev channel) can now be verified against this release.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
.NET
Pull requests that update .NET code
 bug
Something isn't working
 deferred
Agreed follow-up, not scheduled
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 needs-owner
Blocked on an action only the owner can take
 priority
Owner-flagged: work this first
 quality
Standards, simplicity, enforcement
 question
Further information is requested
 refactor
Restructuring without behavior change
 release
Release pipeline / distribution
 wontfix
This will not be worked on
No labels release
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#55