Changelog & versions

Hypercolor is pre-1.0 software under active development. This page explains the version numbering rules and points you at the canonical release notes. It does not mirror per-release notes; those live with the releases themselves.

#How to check your installed version

hypercolor --version

The daemon prints its version on startup and in the status response:

hypercolor status

The REST API surfaces it in every response envelope under meta.api_version.

#Version numbering

Hypercolor uses Semantic Versioning: MAJOR.MINOR.PATCH.

Because the project is pre-1.0, the minor version carries breaking-change weight. A bump from 0.2 to 0.3 may change the REST API envelope, the config file schema, or the effect SDK surface without a deprecation window; the release notes call out every breaking change explicitly. Patch releases (0.3.x) are safe to apply: they contain bug fixes and security hardening only.

#Where release notes live

Release notes have two canonical homes:

• GitHub Releases carries the user-facing notes for every tagged version, alongside the downloadable artifacts.
• CHANGELOG.md at the repository root follows the Keep a Changelog format and is the machine-readable authority.

#Release channels

Public CI updates the Linux, Windows, AUR, npm, and PyPI channels from release tags. Signed macOS artifacts and their Homebrew metadata are promoted manually after the release acceptance checkpoint passes.

The main branch is the working development branch; build it from source (just build) if you want unreleased work. Tagged releases are the stable surface. There is no separate nightly or beta channel.