The release pipeline runs where the project lives #197

New Issue

2026-11-11T05:58:45Z

james.maes commented

2026-11-11 05:58:45 +00:00

From the release reviews of 1.1.1 (2026-11-10). Not part of 1.1.1; planned for 1.2.0 unless said otherwise.

Releases are read from git.kof22.com from 1.1.1 on (ADR 0009), and are still built, signed and published by the workflow on GitHub. Until a pipeline exists on Gitea:

a tag on git.kof22.com builds nothing;
a release's assets are copied to git.kof22.com by hand (outside the attested pipeline, T11);
the packaging pull request is opened on the GitHub copy, while Scoop reads the bucket from Gitea's main;
the winget step submits the download URL on GitHub;
Chocolatey can hold a version before the Scoop manifest names it.

docs/RELEASING.md describes the manual steps. This issue is for removing them. The CI wiring belongs to the Gitea migration work: coordinate there before changing workflows.

From the release reviews of 1.1.1 (2026-11-10). Not part of 1.1.1; planned for 1.2.0 unless said otherwise. Releases are read from `git.kof22.com` from 1.1.1 on (ADR 0009), and are still built, signed and published by the workflow on GitHub. Until a pipeline exists on Gitea: - a tag on `git.kof22.com` builds nothing; - a release's assets are copied to `git.kof22.com` by hand (outside the attested pipeline, T11); - the packaging pull request is opened on the GitHub copy, while Scoop reads the bucket from Gitea's `main`; - the winget step submits the download URL on GitHub; - Chocolatey can hold a version before the Scoop manifest names it. `docs/RELEASING.md` describes the manual steps. This issue is for removing them. The CI wiring belongs to the Gitea migration work: coordinate there before changing workflows.

james.maes added the deferred release labels 2026-11-11 05:58:45 +00:00

james.maes referenced this issue

2026-11-11 06:27:42 +00:00

Release v1.2.0 #200

james.maes referenced this issue

2026-11-11 22:38:24 +00:00

Documents still say 1.1.1; the release is 1.2.0 #218

james.maes commented

2026-11-11 22:38:26 +00:00

For whoever is building the pipeline here (the owner says that work is under way): from this side, main is the 1.2.0 candidate (d5d4f67 plus #217 when it merges); there is no 1.1.1 release, and nothing is to be tagged before this pipeline exists (owner's decisions on #200, which is now the 1.2.0 release issue with draft notes). I am not touching workflows, packaging or docs/RELEASING.md. That document still says 1.1.1 in three places (where releases are read from; the two-prerelease rehearsal): they should read 1.2.0. The rehearsal on #200 (two prereleases, the update read from git.kof22.com from outside the network) still has to be done with the first build this pipeline makes.

For whoever is building the pipeline here (the owner says that work is under way): from this side, main is the 1.2.0 candidate (d5d4f67 plus #217 when it merges); there is no 1.1.1 release, and nothing is to be tagged before this pipeline exists (owner's decisions on #200, which is now the 1.2.0 release issue with draft notes). I am not touching workflows, packaging or docs/RELEASING.md. That document still says 1.1.1 in three places (where releases are read from; the two-prerelease rehearsal): they should read 1.2.0. The rehearsal on #200 (two prereleases, the update read from git.kof22.com from outside the network) still has to be done with the first build this pipeline makes.

james.maes referenced this issue from a commit

2026-11-11 22:40:34 +00:00

docs(release): the documents name 1.2.0 as the release that moves updates to git.kof22.com

james.maes referenced this issue

2026-11-11 22:40:35 +00:00

docs(release): the documents name 1.2.0 as the release that moves updates to git.kof22.com #219

james.maes referenced this issue from a commit

2026-11-11 22:40:55 +00:00

docs(release): the documents name 1.2.0 as the release that moves updates to git.kof22.com (#219)

Sign in to join this conversation.