Kanidm - Support and Release Processes


This document describes the Kanidm project teams support and release version processes.

While we have made every effort to ensure this document is complete, in the event that something is missing or if you have a question, please open a discussion.

The version of this document found on the project page is considered authoritive and applies to all versions.

Release Schedule and Versioning

Kanidm is released on a 3 month (quarterly) schedule.

  • February 1st
  • May 1st
  • August 1st
  • November 1st

Versions follow semver using major.minor.patch with an optional -tag.

  • development branch: X.Y.Z-dev
  • pre-release branch: X.Y.Z-pre
  • stable branch: X.Y.Z

Release branches will be created and tagged 7 days prior to a release. The version will be set to the pre-release version.

  /- tag 1.2.0-dev
  |          tag 1.3.0-dev
  v          v
--o ... --o--o--o--o ...  <- branch master
            \-o--o--o--o--o--o--o  <- branch 1.2.0
              ^        ^  ^
              |        |   tag v1.2.1
              |        \- tag v1.2.0
              \- tag v1.2.0-pre

The first stable release is version 1.2.0. All releases prior are release candidate, beta or alpha builds and will no longer be supported as of the release of 1.2.0.


Stable releases will be supported for 4 months after their release date. This allows a 1 month support overlap between N and N+1 versions.

Stable releases will have the following support provided during their support window.

  • Security fixes
  • Fixes for flaws leading to dataloss or corruption
  • Fixes that impact the ability to upgrade
  • Other quality fixes at the discretion of the project team

Distributions should track the stable branch.


All nodes must be the same version. A topology may contain up to a maximum of 2 nodes.

Upgrade Policy

Upgrades are supported from 1 release (minor version) before the current stable release.

Example: A server running 1.2.0 may upgrade to version 1.3.0. A server running 1.2.0 may not upgrade to 1.4.0.

Tool Versions

Command line tools (kanidm) and sync connectors (kanidm-ipa-sync, kanidm-ldap-sync) must be matched versions with the server that they communicate with at all times.

Unix Clients

The server supports communication from unix clients with a version from 1 release (minor version) before the servers release.

Example: A server running 1.4.0 supports unix clients running 1.4.0 and 1.3.0 of the unix client tools. Unix client tools of 1.2.0 and lower would not be supported.

API stability

Kanidm has a number of APIs with different stability guarantees. APIs that are stable will only recieve breaking changes in the case of an ethics, security or potential data corruption issue.

Stable APIs are:

All other APIs and interactions are not considered stable. Changes will be minimised if possible. This includes but is not limited to:

  • unix domain socket API of kanidm_unixd resolver
  • unix admin domain socket for kanidmd server
  • web user interface design and operations
  • entry schema
  • CLI interface of any command provided by kanidm unless otherwise noted above
  • JSON HTTP end points which use elements from proto/src/internal.rs

Deprecation Policy

Features or APIs may be removed with 1 release versions notice. Deprecations will be announced in the Release Notes

Python module

The python module will typically trail changes in functionality of the core Rust code, and will be developed as we it for our own needs - please feel free to add functionality or improvements, or ask for them in a Github issue!

All code changes will include full type-casting wherever possible.

Project Discretion

In the event of an unforseen or extraordinary situation, the project team may make decisions contradictory to this document at their discretion. In these situation, the project team will make every effort to communicate the reason for the decision and will attempt to minimise disruption to users.