mk6i-open-oscar-server/docs/RELEASE.md

Open OSCAR Server Release Process

This document explains how the Open OSCAR Server release process works.

Overview

Open OSCAR Server is built and released to Github using GoReleaser. The release process, which runs from a local computer (and not a CI/CD process) creates pre-built binaries for several platforms (Windows, macOS, Linux).

GoReleaser runs in a Docker container, which provides a hermetic environment that prevents build contamination from the host environment.

Code Signing Policy

This project offers signed Windows binaries and does not currently offer signed macOS binaries. This means that macOS distrusts Open OSCAR Server by default and quarantines the application when you open it.

If you don't want to bypass this security mechanism, you can build the project yourself instead.

Release Procedure

The following is the procedure that builds Open OSCAR Server and uploads the build artifacts to a Github release.

1. Export Github Personal Access Token (PAT)

Export a Github Personal Access Token that has write:packages permissions for the Open OSCAR Server repo.

```sh
export GITHUB_TOKEN=...
```

1. Tag The Build

Tag the build using semantic versioning.

```shell
git tag v0.1.0
git push --tags
```

1. Dry-Run Release

Execute a dry-run build to make sure all the moving parts work together. Fix any problems that crop up before continuing.

```shell

make release-dry-run

```

1. Release It!

Now run the release process. Once its complete, a private draft release should appear with attached build artifacts.

```shell

make release

```

1. Sign It!

Download the Windows release, sign it, and re-upload the .zip to the draft release created in the previous step.

1. Publish It

Publish the draft release.