Start

Publish the first signed build.

Create an app, connect a publish-only GitHub secret, and let the upload Action complete the draft, upload, and publish sequence.

About 7 setup stepsNo private signing key required

Before you begin

You need a Mateality organization with Releases access, a repository that produces a signed release artifact, and permission to add a GitHub Actions secret and workflow step.

Create the app

Open Apps

From the Releases dashboard, choose Create app.

Choose identity

Enter the app name and claim its globally unique {public-slug}.mateality.app release address.

Choose delivery

Keep stable or add channels, then select Tauri v2 or Generic REST.

Generate a key

Create the publish key and copy it immediately. The full value is not shown again.

Add the GitHub secret

In the repository, open Settings → Secrets and variables → Actions and create MATEALITY_RELEASES_KEY.

Add the publish step

yaml
- name: Publish to Mateality Releases
  uses: mateality/releases-upload@v1
  with:
    api-key: ${{ secrets.MATEALITY_RELEASES_KEY }}
    app: your-app-slug
    version: ${{ github.ref_name }}
    artifact: dist/your-signed-artifact.zip
    target: linux-x86_64
    channel: stable
    notes: ${{ github.event.release.body }}

app is the app slug shown in the dashboard. artifact may be an exact path or a glob, but a glob must resolve to exactly one file. Set target to the identifier your selected updater contract will request.

Confirm the release

The onboarding screen waits for the first published release and refreshes automatically. After the workflow completes:

  1. Open the app’s Releases tab and confirm the version is published.
  2. Open Download page and confirm the expected target is offered.
  3. Configure the Tauri v2 endpoint or test the Generic REST response.

If the workflow fails, use the exact error returned by the Action with Errors & limits.