I version Apprentice with a calendar-based scheme called CalVer. The version is the date I cut the release, so a single glance tells you how recent your build is.
Format vYYYY.MM.DD
Apprentice releases look like v2026.06.26.
- YYYY is the year.
- MM is the month.
- DD is the day I published that release.
A later date is a newer release. If I ship more than one release in a month, each one carries its own date, so v2026.06.26 is newer than v2026.06.20.
These Are Stable Releases
Every dated release is a stable release meant for everyday use. There are no separate alpha, beta, or release-candidate phases.
Stable does not mean bug free. It means the release has been built, tested, and is the version I recommend you run. When a bug is found, it gets fixed in a later dated release.
A Note On Older Versions
Early pre-1.0 builds of Apprentice used SemVer-style pre-release tags such as v1.0.0-alpha.5, v1.0.0-beta.10, or v1.0.0-rc.1. Those phases are finished. Current and future releases use the dated CalVer format above.
If you still run one of those older builds, update to the latest dated release to get the current providers, capabilities, and fixes.
Why CalVer
A date is honest about the thing that matters most to you: how fresh your build is. You do not have to decode whether a change counts as "major" or "minor" to know whether you are behind. Check the date, read the release notes, and update when you want what is new.
Next Step
See Perpetual Fallback License to understand which release your license keeps, and check the release notes for what each dated version includes.