Releases and Versioning
LoginID uses two release streams to balance rapid development with long-term stability.
| Stream | Version Format | Typical Use |
|---|---|---|
| Active Development | 25.x | Latest features and improvements (default SaaS stream) |
| Stable / Maintenance | 2.x | Pinned enterprise deployments |
Stable branches are periodically forked from the Active stream once features reach maturity.
Release streams
Active Development (25.x)
The Active stream is where ongoing development happens.
- New features are introduced here
- Bug fixes land here first
- Default stream for hosted SaaS deployments
Example versions:
25.10.0 → 25.11.0 → 25.12.0
Stable / Maintenance (2.x)
Stable branches provide a controlled release track for enterprise deployments.
- Forked from the Active stream when features mature
- Receives critical fixes and approved backports
- Used for dedicated or pinned environments
Example versions:
2.7.3 → 2.7.4 → 2.7.5
Version numbering
Both streams follow the format:
MAJOR.MINOR.PATCH
Examples:
Active: 25.10.0
Stable: 2.7.5
Branching model
Development moves forward in the Active stream, while stable releases are created from it.
Active: 25.10.0 → 25.11.0 → 25.12.0
│
└── Stable fork → 2.8.0 → 2.8.1
Bug fixes land in Active first, and eligible fixes may be backported to supported Stable releases.
Deployment environments
Separate environments are maintained for:
- Development
- QA
- Production
This applies to the Active stream and each supported Stable branch.
Choosing a stream
Use the stream that matches your deployment model.
| If you are… | Use |
|---|---|
| Using the hosted LoginID SaaS | Active (25.x) |
| Running a dedicated enterprise deployment | Stable (2.x) |
Contact support if you are looking for a dedicated enterprise deployment.