Changelog

Takuhon ships its packages in lockstep: every @takuhon/* package, the bare-name takuhon CLI, and create-takuhon share one version number on each release.

Where releases live

• GitHub Releases — each release is tagged, with a cosign-signed archive and SLSA build provenance.
• npm — packages are published with provenance.
• CHANGELOG.md — the canonical, per-release detail. This page links it rather than duplicating it, so there is a single source of truth.

How versioning works

The version is semantic and anchored to the takuhon.json schema (see Schema stability): a change that could invalidate a currently-valid document is a major release, while new optional fields and features are minor. Because every artifact moves together, the package version doubles as the schema-contract version.

Latest: 1.0.0

1.0.0 (2026-06-30) is the first major release — the profile schema is frozen as a stable contract. additionalProperties is closed everywhere (an unknown or misspelled key is now a validation error), localized values must be non-empty, each array’s ids are unique, and the top-level required set is minimal (every content array is optional). A conforming, closed-safe 0.x document is a valid 1.0.0 document unchanged — run takuhon migrate to stamp the version. See Schema stability for the full contract.

For the complete per-release history, read the CHANGELOG.