@@ -26,39 +26,10 @@ Before upgrading to a newer version, please make sure to check with these docume
2626
2727## Versioning
2828
29- The Ory ecosystem consists of multiple services versioned using [ semantic versioning] ( https://semver.org ) . This section explains
30- how we define service versions and what they mean.
31-
32- ## Development stages
33-
34- :::important
35-
36- ** Ory only releases software that is stable and ready for production!**
37- The sandbox/incubating stage is an indicator of how much the API could change in the future, including backward incompatible
38- changes.
39-
40- Ory was founded in 2015, secures more than 50B requests monthly and is the most trusted open source ecosystem for authentication &
41- authorization.
42-
43- :::
44-
45- There are three main stages of development for services:
46-
47- - ** Graduated:** Mature implementations of proven concepts. They rarely change in backwards incompatible ways. A software is
48- considered graduated if the major version is >= 1, for example ` v1.0.1 ` , ` v2.2.2 ` . Backwards incompatible changes are indicated
49- by a bump of the major version number. Most, if not all, REST APIs will provide backwards compatible transformations that make
50- it possible to interact with the server using older API versions.
51- - ** Incubating:** Implements well defined but not fully matured concepts. Incubating software has a major version number of ` 0 ` ,
52- for example ` v0.10.0 ` . You may see a pre-release version such as ` v0.10.0-beta.1 ` . Incubating software has a higher (but overall
53- moderate) probability for larger changes that can break backwards compatibility, for which there are upgrade guides.
54- - ** Sandbox:** Implements concepts, APIs and CLIs at the experimental stage and may change in unpredictable ways. Sandbox software
55- has a major version number of ` 0 ` with a ` alpha ` or ` beta ` pre-release indicator, for example ` v0.10.0-alpha.1 ` . It's more
56- likely that you'll encounter a version tag with a ` alpha ` pre-release version. We will provide upgrade guides wherever possible,
57- when they're used in production already.
58-
59- The following is a list of maturity level per project:
60-
61- - [ Ory Hydra] ( https://github.com/ory/hydra ) is a ** graduated** project.
62- - [ Ory Kratos] ( https://github.com/ory/kratos ) is a ** graduated** project.
63- - [ Ory Oathkeeper] ( https://github.com/ory/oathkeeper ) is an ** incubating** project.
64- - [ Ory Keto] ( https://github.com/ory/keto ) is a ** sandbox** project.
29+ Ory uses a calendar-based product versioning system, where the version format is ` YY.Q.N ` , representing the year, quarter, and
30+ release number within that quarter. For example, version ` 26.2.0 ` indicates a product release in the second quarter of 2026, with
31+ ` 0 ` being the first release in that quarter. The release number increases with each subsequent release during the quarter. With
32+ this system you can understand when a version was released and how recent it released. Starting from October 2025, all Ory
33+ components use a common versioning number, meaning releases are synchronized across all components such as Ory Kratos, Ory Hydra,
34+ Ory Oathkeeper, and Ory Keto. This unified versioning simplifies upgrades and ensures compatibility across the entire Ory
35+ ecosystem.
0 commit comments