Skip to content

Version scheme

A Stack package or executable may have a version with three or four components: X.Y.Z or X.Y.Z.A.

Development or stable versions

  • Versions with an even Y component are development versions (the master branch)

  • Versions with an odd Y component are stable versions (the stable branch, or in a rc/vX.Y release candidate branch for not-yet-released versions)

Unreleased or released versions

  • Versions with an even Z component are unreleased versions (including release candidates)

  • Versions with an odd Z component are released versions

  • Except for the release branch, all branches must have an even Z component

  • Except for the release, stable and rc/vX.Y release candidate branches, all branches will have a 0 Z component

Use of a fourth component

  • Release candidate binaries will be released with an odd A component

  • Hackage-only dependency compatibility patch releases add a A component (e.g. v2.5.1.1, in the release branch)

  • Pre-release unstable binaries will be released with the date as the A component (e.g. 4.2.0.20260821)

Examples

  • 4.1.0.0: v4.1.* series pre-release branch (rc/v4.1 branch)

  • 4.1.0.1: first release candidate for first release of v4.1.* series (rc/v4.1 branch)

  • 4.1.0.2: continuing development on pre-release branch

  • 4.1.0.3: second release candidate for first release of v4.1.* series (rc/v4.1 branch)

  • 4.1.1: first release of the 4.1.* series (release branch)

  • 4.1.2.1: first release candidate for second release of 4.1.* series (rc/v4.1 branch)

  • 4.1.3: second release of 4.1.* series (release branch)

  • 4.1.3.1: first Hackage-only patch of 4.1.3 (release branch)

  • 4.1.3.2: second Hackage-only patch of 4.1.3 (release branch)

  • 4.2.0: unstable development code (master branch)

  • 4.2.0.20260821: pre-release snapshot of unstable version (master branch)