From dfeeae5b6cba280fb232fb5a6c5bcb3f0e0cb3aa Mon Sep 17 00:00:00 2001 From: J Date: Thu, 8 Oct 2026 06:39:22 -0700 Subject: [PATCH] docs(release): define development artifact families --- README.md | 4 ++++ RELEASING.md | 46 ++++++++++++++++++++++++++++++++++++++++++---- 2 files changed, 46 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 83f8fa5..de412ab 100644 --- a/README.md +++ b/README.md @@ -31,11 +31,15 @@ committed to this Git repository. | Release | Producer | Contents | Consumer | | --- | --- | --- | --- | | `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 | Every release must include SHA-256 checksums. A runtime release also includes the machine-readable metadata used to update the public runtime manifest in [`openminion/openminion`](https://github.com/openminion/openminion). +Development releases are marked as prereleases and never enter a stable update +manifest. Runtime and Desktop versions are independent. ## Download flow diff --git a/RELEASING.md b/RELEASING.md index 7b4d5d9..64bb8b6 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -11,16 +11,33 @@ Runtime releases use: runtime-v-build. ``` +Unsigned runtime development releases use: + +```text +runtime-dev-v-build. +``` + Desktop releases use: ```text desktop-v ``` +Unsigned Desktop development releases use: + +```text +desktop-dev-v-build. +``` + Release tags are immutable. If packaging changes without a new runtime source version, publish the next runtime build number instead of replacing an existing release. +Development releases are always GitHub prereleases. Their release notes and +machine-readable metadata must say that they are unsigned, not notarized, not +stable-manifest eligible, and not automatic-update eligible. Runtime and +Desktop versions are independent. + ## Runtime assets A qualified target contributes two executables with matching version and target @@ -43,9 +60,11 @@ SHA256SUMS ``` `runtime-release.json` records the runtime source revision, packaging revision, -target metadata, filenames, sizes, and SHA-256 digests. The public manifest in -`openminion/openminion` may reference a target only after these exact release -assets are publicly reachable and independently verified. +target metadata, filenames, sizes, and SHA-256 digests. The public stable +manifest in `openminion/openminion` may reference a target only after these +exact release assets are publicly reachable, independently verified, signed, +native-qualified, and Desktop-qualified. Unsigned development releases never +enter that manifest. ## Desktop assets @@ -59,7 +78,26 @@ SHA256SUMS 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. +supported Desktop release or stable update. + +## Unsigned development fallback + +Until stable signing and qualification are available, every final OpenMinion +source release must still publish a complete +`runtime-dev-v-build.` prerelease containing paired CLI and +daemon binaries for macOS arm64, Linux x86_64, and Windows x86_64, every +artifact `.json` and `.sha256` sidecar, `runtime-release.json`, and +`SHA256SUMS`. + +Each reviewed Desktop development release similarly publishes every macOS, +Linux, and Windows package under +`desktop-dev-v-build.`, with `desktop-release.json` +and `SHA256SUMS`. It does not inherit the runtime version. + +For both release families, download every public asset anonymously and verify +all digests before deleting the producer's private transfer draft. Public +availability does not waive signing, native trust, Desktop compatibility, or +stable-manifest gates. ## Producer workflow