docs: switch to calendar-based unified versioning #2326
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
unatasha8
reviewed
Oct 20, 2025
| 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 |
There was a problem hiding this comment.
Suggested change
| 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 |
unatasha8
reviewed
Oct 20, 2025
| 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 |
There was a problem hiding this comment.
Suggested change
| 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 |
unatasha8
reviewed
Oct 20, 2025
| - [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 |
There was a problem hiding this comment.
Suggested change
| 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 |
unatasha8
reviewed
Oct 20, 2025
| - [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 |
There was a problem hiding this comment.
Suggested change
| 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 |
unatasha8
reviewed
Oct 20, 2025
| - [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 |
There was a problem hiding this comment.
Suggested change
| 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 |
unatasha8
reviewed
Oct 20, 2025
| 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 |
There was a problem hiding this comment.
Suggested change
| version number, meaning releases are synchronized across all components such as Kratos, Hydra, Oathkeeper, and Keto. This unified | |
| version number, meaning releases are synchronized across all components such as Ory Kratos, Ory Hydra, Ory Oathkeeper, Ory Keto, and Ory Polis. This unified |
unatasha8
requested changes
Oct 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue or Design Document
Checklist
If this pull request addresses a security vulnerability,
I confirm that I got approval (please contact security@ory.sh) from the maintainers to push the changes.
Further comments