Fission

Versioning policy

Last verified: 2026-05-02

Semantic versioning

Fission follows SemVer (MAJOR.MINOR.PATCH), including during 0.y.z:

• MAJOR (including 0 → 1): Breaking changes to documented CLI contracts, artifact JSON schemas promised as stable in docs/EVALUATION.md, or installation/layout guarantees described in release notes.
• MINOR: Backward-compatible CLI additions, new optional flags, additive JSON fields (clients must tolerate unknown keys), performance improvements without contract breaks.
• PATCH: Bug fixes and internal refactors that do not change outward contracts.

While in 0.x, minor releases may still introduce significant behavior changes if they are flagged in release notes and evaluation docs; patch releases should remain low-risk.

Tags and GitHub Releases

• Release tags match vMAJOR.MINOR.PATCH (for example v0.4.2).
• Continuous delivery builds from tag pushes per .github/workflows/cd.yml.

Branches

• main is the integration branch; tags are cut from commits that pass merge gates described in CONTRIBUTING.md.
• Long-lived release branches are optional; if adopted later, document them here and in docs/RELEASE.md.

Pre-releases

If you need -alpha / -beta suffixes, prefer GitHub prerelease toggles plus clear notes; keep tag names consistent with tooling expectations in cd.yml.

This site is open source. Improve this page.