Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,25 @@ committed to this Git repository.
| --- | --- | --- | --- |
| `runtime-v<version>-build.<number>` | private `openminion-packaging` workflow | paired `openminion` and `openminiond` executables for each qualified platform | OpenMinion Desktop and direct CLI users |
| `runtime-dev-v<version>-build.<number>` | private `openminion-packaging` workflow | unsigned paired executables and verification sidecars for macOS, Linux, and Windows | Development testing and direct downloads |
| `desktop-v<version>` | `openminion/desktop` workflow | signed installers or archives for each qualified platform | Desktop users |
| `desktop-dev-v<version>-build.<number>` | `openminion/desktop` workflow | unsigned installers or archives for macOS, Linux, and Windows | Desktop development testing |
| `desktop-v<version>` | `openminion/desktop` workflow | signed binary installers or application archives for each qualified platform | Desktop users |
| `desktop-dev-v<version>-build.<number>` | `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
[`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.

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.
Expand Down
14 changes: 12 additions & 2 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading