Skip to content

Commit dfdb558

Browse files
authored
ci(release): stop scheduled desktop preview builds (#3425)
Removes the 6-hourly `schedule` trigger from the Desktop previews workflow. Previews now run only on `workflow_dispatch`, with the existing `candidates` and `promote_version` inputs unchanged. Updates `docs/releases.md` to describe dispatch-only previews. --------- Signed-off-by: Will Pfleger <[email protected]>
1 parent ed68067 commit dfdb558

2 files changed

Lines changed: 3 additions & 6 deletions

File tree

‎.github/workflows/release.yml‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,6 @@ on:
1111
description: Promote a validated version (e.g. 0.7.0-preview.22.1) to the preview updater feed; no build
1212
type: string
1313
default: ""
14-
schedule:
15-
- cron: "17 */6 * * *"
1614

1715
permissions:
1816
contents: read

‎docs/releases.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ checked against each job's checksums before assembly. If a job fails, use
3333
and publication rejects mixed-version artifacts. Windows/Linux previews are not
3434
Authenticode-signed Windows releases or evidence of completed desktop acceptance.
3535

36-
Runs are scheduled at **00:17, 06:17, 12:17, and 18:17 UTC**. To start one manually:
36+
Previews run only when someone dispatches the workflow:
3737

3838
```sh
3939
gh workflow run release.yml --repo block/buzz-app --ref main
@@ -59,7 +59,6 @@ administrator password.
5959

6060
The release automatically promotes each eligible build to the rolling preview
6161
feed after the signed prerelease is published and the promotion gate passes.
62-
This includes scheduled runs and manual builds without `promote_version`.
6362
An updater-less artifact, invalid signature, or rollback leaves the existing feed
6463
unchanged, but the promotion job fails and needs investigation. The workflow
6564
does **not** publish to the legacy `block/buzz` updater. Older installed apps
@@ -124,7 +123,7 @@ and compares the GitHub API asset; this is not evidence of public endpoint
124123
availability. Confirm the endpoint in an installed client after the first
125124
promotion. GitHub asset replacement can briefly return 404 while the old asset
126125
is replaced. Promotion is serialized with the release workflow, and a failed
127-
upload needs investigation before the next scheduled run.
126+
upload needs investigation before the next preview run.
128127
Recover from a broken feed by promoting a higher tested build; for key loss or
129128
client failure, distribute a manually installed build (an Apple-signed DMG on macOS). Do not assume
130129
rolling back a signed archive can undo an installed update.
@@ -466,7 +465,7 @@ gh workflow run release.yml --repo block/buzz-app \
466465
--ref <candidate-branch> -f candidates=true
467466
```
468467

469-
Scheduled runs and dispatches without this switch build and publish all three
468+
Dispatches without this switch build and publish all three
470469
platforms. A `promote_version` recovery run skips all platform builds and only
471470
updates the feed. Candidate-only runs remain artifact-only, are built without the updater, and can run from
472471
a feature branch, without signing credentials or publication. They use the same

0 commit comments

Comments
 (0)