Stability and versioning
A high version number and frequent releases do not mean origam breaks often. This page says what the number means, how releases are cut and where changes are written down.
What the 2.x number means
The 2.x number is historical. In practice origam is a pre-1.0 project that carries a 2.x label.
Below 3.0.0, the minor and patch numbers are bookkeeping, not a compatibility contract.
Why releases are frequent
Every merged change to the published package gets its own patch release. Changes are not held back to be batched into a weekly or monthly release, so the patch number climbs quickly.
A patch is a bug fix. A minor is a medium feature with limited impact on existing usage. Changes that do not touch the published package, such as this site, the documentation, the tests or the tooling, produce no release at all.
How breaking changes ship
Until 3.0.0, a breaking change can ship in a minor release. It is then documented explicitly and honestly in the CHANGELOG.
The CHANGELOG is where to look before upgrading across a minor version.
Read the changelogWhat 3.0.0 will be
3.0.0 is reserved for splitting the package into modules. It will be the first announced major breaking release.
Nothing else ships under that number: not a batch of bug fixes, not a dependency upgrade. This page gives no date for it.
See the roadmapDeprecation policy
There is no long deprecation cycle. At the current stage of the project the clean break is preferred to a compatibility layer: a deprecated API is removed as soon as someone gets to it, in a minor release, and the removal is written in the CHANGELOG.
Deprecations that were announced for the next major are not held back until 3.0.0. This is a rule for the current stage of the project, not a permanent guarantee.
What this page does not promise
This page describes how versions are numbered and announced. origam publishes no long-term-support line, no support window and no guaranteed response time.