Mateality Releases

From signed build to dependable update.

Publish desktop app artifacts from CI, serve updater-specific responses, and give people a hosted place to download each release.

Tauri v2Generic RESTGitHub Actions

Mateality Releases begins after your build. Your CI environment continues to compile and sign the application. Releases receives the finished artifact, stores its declared integrity metadata and optional signature, and delivers it to updater clients and browsers.

Publish

App-scoped publish keys authorize automation to create drafts, upload artifacts, and publish them.

Adapt

A release stays framework-neutral. The selected adapter renders either a Tauri v2 response or the Generic REST contract.

Deliver

The same published files power updater downloads, the public read API, and the hosted download page.

The supported path

Create an app

Choose the app name, public address, release channels, and either the Tauri v2 or Generic REST adapter.

Connect CI

Generate a publish key, save it once, and add it to GitHub as MATEALITY_RELEASES_KEY.

Upload after signing

Run mateality/releases-upload@v1 after the signed build has produced exactly one artifact for that Action step.

Check and download

Point the client at the app’s updater endpoint or consume the public read API.

Choose what you need

Follow the Quickstart for the shortest production path.
Read Core concepts before designing channels and targets.
Use GitHub Action for the supported end-to-end publish workflow.
Configure Tauri v2 or Generic REST.
Open Troubleshooting when a key, draft, upload, or updater check fails.

What is not currently supported

Electron updater feeds are not enabled in the adapter registry or app creation UI. The user-facing adapter choices are Tauri v2 and Generic REST.