From bce77a9969c3710892a073fa9aba3d88e7c02b8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adam=20Wa=C5=82ach?= Date: Mon, 20 Oct 2025 11:59:28 +0200 Subject: [PATCH 1/8] docs: switch to calendar-based unified versioning --- docs/ecosystem/upgrading.mdx | 42 ++++++------------------------------ 1 file changed, 6 insertions(+), 36 deletions(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index 2ee422474..bcc5de7f5 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -26,39 +26,9 @@ Before upgrading to a newer version, please make sure to check with these docume ## Versioning -The Ory ecosystem consists of multiple services versioned using [semantic versioning](https://semver.org). This section explains -how we define service versions and what they mean. - -## Development stages - -:::important - -**Ory only releases software that is stable and ready for production!** -The sandbox/incubating stage is an indicator of how much the API could change in the future, including backward incompatible -changes. - -Ory was founded in 2015, secures more than 50B requests monthly and is the most trusted open source ecosystem for authentication & -authorization. - -::: - -There are three main stages of development for services: - -- **Graduated:** Mature implementations of proven concepts. They rarely change in backwards incompatible ways. A software is - considered graduated if the major version is >= 1, for example `v1.0.1`, `v2.2.2`. Backwards incompatible changes are indicated - by a bump of the major version number. Most, if not all, REST APIs will provide backwards compatible transformations that make - it possible to interact with the server using older API versions. -- **Incubating:** Implements well defined but not fully matured concepts. Incubating software has a major version number of `0`, - 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 - moderate) probability for larger changes that can break backwards compatibility, for which there are upgrade guides. -- **Sandbox:** Implements concepts, APIs and CLIs at the experimental stage and may change in unpredictable ways. Sandbox software - 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 - likely that you'll encounter a version tag with a `alpha` pre-release version. We will provide upgrade guides wherever possible, - when they're used in production already. - -The following is a list of maturity level per project: - -- [Ory Hydra](https://github.com/ory/hydra) is a **graduated** project. -- [Ory Kratos](https://github.com/ory/kratos) is a **graduated** project. -- [Ory Oathkeeper](https://github.com/ory/oathkeeper) is an **incubating** project. -- [Ory Keto](https://github.com/ory/keto) is a **sandbox** project. +Ory uses a calendar-based versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release +number within that quarter. For example, version `25.2.0` indicates a release in the second quarter of 2025, with `0` being the +first release in that quarter. The release number increases with each subsequent release during the quarter. This system helps +users understand when a version was released and how recent it is. Starting from October 2025, all Ory components use a common +version number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified +versioning simplifies upgrades and ensures compatibility across the entire Ory ecosystem. From 865d4c82088824f670499759b673f34cdcaea0c4 Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Thu, 6 Nov 2025 14:14:54 -0800 Subject: [PATCH 2/8] Update docs/ecosystem/upgrading.mdx --- docs/ecosystem/upgrading.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index bcc5de7f5..ee86700de 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -29,6 +29,6 @@ Before upgrading to a newer version, please make sure to check with these docume Ory uses a calendar-based versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release number within that quarter. For example, version `25.2.0` indicates a release in the second quarter of 2025, with `0` being the first release in that quarter. The release number increases with each subsequent release during the quarter. This system helps -users understand when a version was released and how recent it is. Starting from October 2025, all Ory components use a common +you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common version number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified versioning simplifies upgrades and ensures compatibility across the entire Ory ecosystem. From b3273a696ffc9a504e95120f52b319fb7b8ecc13 Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Thu, 6 Nov 2025 14:15:03 -0800 Subject: [PATCH 3/8] Update docs/ecosystem/upgrading.mdx --- docs/ecosystem/upgrading.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index ee86700de..58da891a3 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -30,5 +30,5 @@ Ory uses a calendar-based versioning system, where the version format is `YY.Q.N number within that quarter. For example, version `25.2.0` indicates a release in the second quarter of 2025, with `0` being the first release in that quarter. The release number increases with each subsequent release during the quarter. This system helps you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common -version number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified +versioning number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified versioning simplifies upgrades and ensures compatibility across the entire Ory ecosystem. From ae4d590636dca48dda98d31e03b6d3e0fecb62eb Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Thu, 6 Nov 2025 14:15:19 -0800 Subject: [PATCH 4/8] Update docs/ecosystem/upgrading.mdx --- docs/ecosystem/upgrading.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index 58da891a3..003fd11ed 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -28,7 +28,7 @@ Before upgrading to a newer version, please make sure to check with these docume Ory uses a calendar-based versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release number within that quarter. For example, version `25.2.0` indicates a release in the second quarter of 2025, with `0` being the -first release in that quarter. The release number increases with each subsequent release during the quarter. This system helps +first release in that quarter. The release number increases with each subsequent release during the quarter. With this system you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common versioning number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified versioning simplifies upgrades and ensures compatibility across the entire Ory ecosystem. From 1f185e7d3788d6a2c574b44349f07d74724bd99a Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Thu, 6 Nov 2025 14:15:33 -0800 Subject: [PATCH 5/8] Update docs/ecosystem/upgrading.mdx --- docs/ecosystem/upgrading.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index 003fd11ed..11979cdaa 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -26,7 +26,7 @@ Before upgrading to a newer version, please make sure to check with these docume ## Versioning -Ory uses a calendar-based versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release +Ory uses a calendar-based product versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release number within that quarter. For example, version `25.2.0` indicates a release in the second quarter of 2025, with `0` being the first release in that quarter. The release number increases with each subsequent release during the quarter. With this system you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common From bfcef1aa3002cc19040de4839921fb383aaa6081 Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Thu, 6 Nov 2025 14:15:47 -0800 Subject: [PATCH 6/8] Update docs/ecosystem/upgrading.mdx --- docs/ecosystem/upgrading.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index 11979cdaa..aebadfda7 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -27,7 +27,7 @@ Before upgrading to a newer version, please make sure to check with these docume ## Versioning Ory uses a calendar-based product versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release -number within that quarter. For example, version `25.2.0` indicates a release in the second quarter of 2025, with `0` being the +number within that quarter. For example, version `26.2.0` indicates a product release in the second quarter of 2026, with `0` being the first release in that quarter. The release number increases with each subsequent release during the quarter. With this system you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common versioning number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified From 3bece883ac20fe9e548b2fa29994d1fe4d197c2c Mon Sep 17 00:00:00 2001 From: unatasha8 Date: Thu, 6 Nov 2025 14:18:05 -0800 Subject: [PATCH 7/8] Update docs/ecosystem/upgrading.mdx --- docs/ecosystem/upgrading.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index aebadfda7..fdef76d1a 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -30,5 +30,5 @@ Ory uses a calendar-based product versioning system, where the version format is number within that quarter. For example, version `26.2.0` indicates a product release in the second quarter of 2026, with `0` being the first release in that quarter. The release number increases with each subsequent release during the quarter. With this system you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common -versioning number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified +versioning number, meaning releases are synchronized across all components such as Ory Kratos, Ory Hydra, Ory Oathkeeper, and Ory Keto. This unified versioning simplifies upgrades and ensures compatibility across the entire Ory ecosystem. From e169099d224cece11842e5d9e9310f0937aa2f15 Mon Sep 17 00:00:00 2001 From: vinckr Date: Mon, 10 Nov 2025 11:13:23 -0300 Subject: [PATCH 8/8] chore: format --- docs/ecosystem/upgrading.mdx | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/ecosystem/upgrading.mdx b/docs/ecosystem/upgrading.mdx index fdef76d1a..e437960dd 100644 --- a/docs/ecosystem/upgrading.mdx +++ b/docs/ecosystem/upgrading.mdx @@ -26,9 +26,10 @@ Before upgrading to a newer version, please make sure to check with these docume ## Versioning -Ory uses a calendar-based product versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and release -number within that quarter. For example, version `26.2.0` indicates a product release in the second quarter of 2026, with `0` being the -first release in that quarter. The release number increases with each subsequent release during the quarter. With this system -you can understand when a version was released and how recent it released. Starting from October 2025, all Ory components use a common -versioning number, meaning releases are synchronized across all components such as Ory Kratos, Ory Hydra, Ory Oathkeeper, and Ory Keto. This unified -versioning simplifies upgrades and ensures compatibility across the entire Ory ecosystem. +Ory uses a calendar-based product versioning system, where the version format is `YY.Q.N`, representing the year, quarter, and +release number within that quarter. For example, version `26.2.0` indicates a product release in the second quarter of 2026, with +`0` being the first release in that quarter. The release number increases with each subsequent release during the quarter. With +this system you can understand when a version was released and how recent it released. Starting from October 2025, all Ory +components use a common versioning number, meaning releases are synchronized across all components such as Ory Kratos, Ory Hydra, +Ory Oathkeeper, and Ory Keto. This unified versioning simplifies upgrades and ensures compatibility across the entire Ory +ecosystem.