Skip to content
openminionPublic

About

Public release artifacts for the OpenMinion runtime and Desktop app.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

OpenMinion logo

OpenMinion Releases

Public runtime and Desktop release artifacts.

OpenMinion · Desktop · Website

CI License

Public binary releases for the OpenMinion runtime and Desktop app.

This repository is the download boundary for artifacts produced and verified by the OpenMinion build repositories. Binary files are published through GitHub Releases; they are not committed to this Git repository.

Release families

Release Producer Contents Consumer
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 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. Development binaries use normal GitHub Releases so the download pages remain visible with the other releases. Their -dev- tags, manifests, and notes must identify them as unsigned and non-stable, and they 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.
  2. The producer creates a draft release here and uploads the exact verified files.
  3. The public files are downloaded again and checked before the release is published.
  4. Runtime manifests are promoted only after their referenced files are public and verified.

Publishing details and artifact naming are defined in RELEASING.md.

Source repositories

  • OpenMinion — runtime source, Python packages, and runtime manifests
  • OpenMinion Desktop — Desktop source
  • openminion-packaging — private native runtime build and qualification

Repository boundary

This repository contains release policy and lightweight validation only. It does not contain OpenMinion source code, Desktop source code, signing material, or committed binary artifacts.

Report security issues privately as described in SECURITY.md.

License

Repository content is licensed under the Apache License, Version 2.0. Each release asset retains the license and notices of its producing project and included dependencies.

About

Public release artifacts for the OpenMinion runtime and Desktop app.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages