From 3d47127c29d9a9d9c96df2e37f8448b67aadd6ef Mon Sep 17 00:00:00 2001 From: J Date: Thu, 8 Oct 2026 16:57:35 -0700 Subject: [PATCH] docs(release): keep desktop artifacts binary-only --- README.md | 14 ++++++++++++-- RELEASING.md | 14 ++++++++++++-- 2 files changed, 24 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index de412ab..81acc11 100644 --- a/README.md +++ b/README.md @@ -32,8 +32,8 @@ committed to this Git repository. | --- | --- | --- | --- | | `runtime-v-build.` | private `openminion-packaging` workflow | paired `openminion` and `openminiond` executables for each qualified platform | OpenMinion Desktop and direct CLI users | | `runtime-dev-v-build.` | private `openminion-packaging` workflow | unsigned paired executables and verification sidecars for macOS, Linux, and Windows | Development testing and direct downloads | -| `desktop-v` | `openminion/desktop` workflow | signed installers or archives for each qualified platform | Desktop users | -| `desktop-dev-v-build.` | `openminion/desktop` workflow | unsigned installers or archives for macOS, Linux, and Windows | Desktop development testing | +| `desktop-v` | `openminion/desktop` workflow | signed binary installers or application archives for each qualified platform | Desktop users | +| `desktop-dev-v-build.` | `openminion/desktop` workflow | unsigned binary installers or application archives for macOS, Linux, and Windows | Desktop development testing | Every release must include SHA-256 checksums. A runtime release also includes the machine-readable metadata used to update the public runtime manifest in @@ -41,6 +41,16 @@ the machine-readable metadata used to update the public runtime manifest in Development releases are marked as prereleases and never enter a stable update manifest. Runtime and Desktop versions are independent. +Desktop release assets are binary-only. Producers may upload installers, +executable application archives, checksums, release metadata, and platform +signature or provenance files. They must not upload Desktop source checkouts, +source archives, repository exports, or unpacked project trees. + +GitHub automatically displays `Source code (zip)` and `Source code (tar.gz)` +for every tagged release. Those links are snapshots of this small public +release-policy repository, not the Desktop source repository or a Desktop +release asset. + ## Download flow 1. A producer repository builds and tests the artifacts on GitHub Actions. diff --git a/RELEASING.md b/RELEASING.md index 64bb8b6..542558a 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -68,14 +68,24 @@ enter that manifest. ## Desktop assets -Desktop releases contain the installers or archives produced by the certified -Desktop workflow for each supported platform, plus: +Desktop releases contain only the binary installers or executable application +archives produced by the certified Desktop workflow for each supported +platform, plus: ```text desktop-release.json SHA256SUMS ``` +Optional platform signature and provenance files are also allowed. Do not +upload Desktop source checkouts, source archives, repository exports, Electron +project bundles, or unpacked project trees to this repository's releases. + +GitHub's automatic `Source code (zip)` and `Source code (tar.gz)` links cannot +be removed from a tagged release. They snapshot this public release-policy +repository only; they are not uploaded Desktop assets and do not contain the +Desktop source repository. + The release notes must state which platforms are signed, notarized, and clean-machine tested. An unsigned development build must not be presented as a supported Desktop release or stable update.