Tag v0.1.0-beta.1 (dev channel) once CI is green on main, and verify the whole chain: tag → release workflow → GitHub Release with gclo-dev-Setup.exe + portable + delta assets + gclo-cli-win-x64.zip → install → in-app Check for updates detects and applies a subsequent release. Then first stable v0.1.0.
Watch-list from the CI/CD agent (unverified-by-execution):
vpk download github flag spelling (--pre/--channel) — step is continue-on-error; only delta generation is at risk.
Release dotnet publish runs with PublishTrimmed=true (Release default in csproj): watch for IL2xxx trim warnings from Velopack; set -p:PublishTrimmed=false if it fights back (already done for the app publish; check the CLI).
dependency-review allow-license SPDX WITH expressions may need simplifying.
Coverage gate assumes cobertura package name gclo.Engine.
Tag `v0.1.0-beta.1` (dev channel) once CI is green on main, and verify the whole chain: tag → release workflow → GitHub Release with `gclo-dev-Setup.exe` + portable + delta assets + `gclo-cli-win-x64.zip` → install → in-app **Check for updates** detects and applies a subsequent release. Then first stable `v0.1.0`.
Watch-list from the CI/CD agent (unverified-by-execution):
- `vpk download github` flag spelling (`--pre`/`--channel`) — step is continue-on-error; only delta generation is at risk.
- Release `dotnet publish` runs with `PublishTrimmed=true` (Release default in csproj): watch for IL2xxx trim warnings from Velopack; set `-p:PublishTrimmed=false` if it fights back (already done for the app publish; check the CLI).
- dependency-review allow-license SPDX `WITH` expressions may need simplifying.
- Coverage gate assumes cobertura package name `gclo.Engine`.
Pipeline proven twice: beta.2 (first complete release) and beta.3 (ships #2 path recovery; created as draft->assets->changelog->publish per the immutable-release fix). Remaining for this issue: install gclo-dev-Setup.exe from beta.2 or earlier, then Help > Check for updates should find beta.3 and update-and-restart — needs an interactive desktop, owner to confirm. After that: first stable tag v0.1.0.
Pipeline proven twice: beta.2 (first complete release) and beta.3 (ships #2 path recovery; created as draft->assets->changelog->publish per the immutable-release fix). Remaining for this issue: install gclo-dev-Setup.exe from beta.2 or earlier, then Help > Check for updates should find beta.3 and update-and-restart — needs an interactive desktop, owner to confirm. After that: first stable tag v0.1.0.
Beta pipeline fully proven. 13 dev betas (v0.1.0-beta.1 → beta.13) have each gone tag → release workflow → GitHub Release with the full asset set (gclo-dev-Setup.exe, Portable, full + delta .nupkg, gclo-cli-win-x64.zip, releases.dev.json). Delta generation works; the coverage-gate note is moot (the gate now enforces 100% across three packages, not a 60% gclo.Engine assumption); no trim/publish fights materialized.
Remaining before this closes:
Owner-verify Check for updates applies a newer release in an installed build (the dev-channel discovery bug that would have blocked this was fixed in beta.12).
Cut the first stablev0.1.0 (needs #7 publishing secrets first).
**Beta pipeline fully proven.** 13 dev betas (v0.1.0-beta.1 → beta.13) have each gone tag → release workflow → GitHub Release with the full asset set (`gclo-dev-Setup.exe`, Portable, full + delta `.nupkg`, `gclo-cli-win-x64.zip`, `releases.dev.json`). Delta generation works; the coverage-gate note is moot (the gate now enforces 100% across three packages, not a 60% `gclo.Engine` assumption); no trim/publish fights materialized.
**Remaining before this closes:**
- [ ] Owner-verify **Check for updates** applies a newer release in an installed build (the dev-channel discovery bug that would have blocked this was fixed in beta.12).
- [ ] Cut the first **stable** `v0.1.0` (needs #7 publishing secrets first).
✅Self-update verified on a real install (owner-confirmed): a v0.1.0-beta.11 install ran Help → Check for updates, found v0.1.0-beta.13, and updated + relaunched successfully. The dev-channel discovery fix (beta.12) works. Only the first stable v0.1.0 (gated on #7 secrets) remains before this closes.
✅ **Self-update verified on a real install** (owner-confirmed): a v0.1.0-beta.11 install ran Help → Check for updates, found v0.1.0-beta.13, and updated + relaunched successfully. The dev-channel discovery fix (beta.12) works. Only the first **stable** v0.1.0 (gated on #7 secrets) remains before this closes.
Marked as latest (non-prerelease) with the full stable asset set: gclo-stable-Setup.exe, gclo-stable-Portable.zip, gclo-cli-win-x64.zip, the full package, and releases.stable.json. Beta pipeline was proven across 15 dev betas; self-update was owner-verified on a real install. The whole tag → workflow → GitHub Release chain works end to end for both channels.
NuGet and winget publishing were skipped (no secrets configured) — tracked in #7.
🎉 **v1.0.0 shipped** — the first stable release is live: https://github.com/KofTwentyTwo/gclo/releases/tag/v1.0.0
Marked as latest (non-prerelease) with the full stable asset set: `gclo-stable-Setup.exe`, `gclo-stable-Portable.zip`, `gclo-cli-win-x64.zip`, the full package, and `releases.stable.json`. Beta pipeline was proven across 15 dev betas; self-update was owner-verified on a real install. The whole tag → workflow → GitHub Release chain works end to end for both channels.
NuGet and winget publishing were skipped (no secrets configured) — tracked in #7.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Tag
v0.1.0-beta.1(dev channel) once CI is green on main, and verify the whole chain: tag → release workflow → GitHub Release withgclo-dev-Setup.exe+ portable + delta assets +gclo-cli-win-x64.zip→ install → in-app Check for updates detects and applies a subsequent release. Then first stablev0.1.0.Watch-list from the CI/CD agent (unverified-by-execution):
vpk download githubflag spelling (--pre/--channel) — step is continue-on-error; only delta generation is at risk.dotnet publishruns withPublishTrimmed=true(Release default in csproj): watch for IL2xxx trim warnings from Velopack; set-p:PublishTrimmed=falseif it fights back (already done for the app publish; check the CLI).WITHexpressions may need simplifying.gclo.Engine.Pipeline proven twice: beta.2 (first complete release) and beta.3 (ships #2 path recovery; created as draft->assets->changelog->publish per the immutable-release fix). Remaining for this issue: install gclo-dev-Setup.exe from beta.2 or earlier, then Help > Check for updates should find beta.3 and update-and-restart — needs an interactive desktop, owner to confirm. After that: first stable tag v0.1.0.
Beta pipeline fully proven. 13 dev betas (v0.1.0-beta.1 → beta.13) have each gone tag → release workflow → GitHub Release with the full asset set (
gclo-dev-Setup.exe, Portable, full + delta.nupkg,gclo-cli-win-x64.zip,releases.dev.json). Delta generation works; the coverage-gate note is moot (the gate now enforces 100% across three packages, not a 60%gclo.Engineassumption); no trim/publish fights materialized.Remaining before this closes:
v0.1.0(needs #7 publishing secrets first).✅ Self-update verified on a real install (owner-confirmed): a v0.1.0-beta.11 install ran Help → Check for updates, found v0.1.0-beta.13, and updated + relaunched successfully. The dev-channel discovery fix (beta.12) works. Only the first stable v0.1.0 (gated on #7 secrets) remains before this closes.
🎉 v1.0.0 shipped — the first stable release is live: https://github.com/KofTwentyTwo/gclo/releases/tag/v1.0.0
Marked as latest (non-prerelease) with the full stable asset set:
gclo-stable-Setup.exe,gclo-stable-Portable.zip,gclo-cli-win-x64.zip, the full package, andreleases.stable.json. Beta pipeline was proven across 15 dev betas; self-update was owner-verified on a real install. The whole tag → workflow → GitHub Release chain works end to end for both channels.NuGet and winget publishing were skipped (no secrets configured) — tracked in #7.