Release Process¶

Semaphore Chat uses a tag-based release workflow with support for full releases, component hotfixes, and manual builds.

Tag Patterns¶

Creating a Release¶

Full Release¶

git checkout main
git pull origin main

# Update CHANGELOG.md, commit
git add CHANGELOG.md
git commit -m "docs: update changelog for v1.0.0"

# Tag and push
git tag v1.0.0
git push origin main
git push origin v1.0.0

This triggers:

• Electron builds for Windows (.exe) and Linux (.AppImage, .deb, .rpm)
• Docker images published to GHCR (backend + frontend)
• Helm chart published to GHCR
• GitHub Release created with all Electron artifacts
• Auto-update manifests uploaded (latest.yml, latest-linux.yml)

Component Hotfixes¶

# Electron only
git tag electron-v1.0.1 && git push origin electron-v1.0.1

# Docker images only
git tag docker-v1.0.1 && git push origin docker-v1.0.1

# Helm chart only
git tag helm-v1.0.1 && git push origin helm-v1.0.1

Manual Build¶

Go to GitHub Actions, select the workflow, click "Run workflow", optionally specify a version.

Release Artifacts¶

GitHub Release (Electron)¶

Docker Images (GHCR)¶

ghcr.io/OWNER/semaphore-backend:1.0.0
ghcr.io/OWNER/semaphore-frontend:1.0.0

Tags: 1.0.0, 1.0, 1, latest

Helm Chart (GHCR OCI)¶

helm install semaphore-chat oci://ghcr.io/OWNER/semaphore-chat/charts/semaphore-chat --version 1.0.0

Electron Auto-Update¶

The desktop app checks for updates on startup (3s delay) and every hour. Uses GitHub Releases as the update source.

Requirements: latest.yml must exist in the release, release must not be draft/prerelease.

Version Management¶

Versions are injected from git tags during CI -- no need to manually update package.json or Chart.yaml.

Follow Semantic Versioning: MAJOR (breaking), MINOR (features), PATCH (fixes).

Troubleshooting¶