Secret Server Release Cadence
Delinea is committed to delivering continuous improvements to Secret Server through a structured release process. This article describes the release cadence for both Secret Server Cloud and Secret Server On-Premises deployments.
Secret Server Cloud
Secret Server Cloud follows a continuous delivery model. Updates are deployed through an automated CI/CD pipeline, delivering new features, enhancements, security updates, and defect fixes on an ongoing basis. Cloud customers automatically receive the latest capabilities without needing to plan or execute upgrade procedures. Secret Server Cloud "releases" are referred to by date, not version numbers.
For details on individual cloud updates, see the Secret Server Change Log.
Secret Server On-Premises
On-premises releases are derived from a point-in-time cloud release and undergo an additional round of QA and infrastructure testing to validate the deployment for on-premises environments. This process ensures that on-premises customers receive the same capabilities delivered to cloud, packaged and verified for self-hosted deployments. A small number of features may be unavailable in on-premises releases, particularly where functionality is dependent on the
Version Numbers and Release Types
On-premises version numbers follow this format:
<major version number (annual code)>.<feature release number>.<maintenance release number (build)>
Examples include 11.3.000012 and 12.1.000008
As the format shows, Secret Server On-Premises follows a structured release cadence consisting of two release types:
Feature Releases
A feature release delivers new functionality, integrations, platform enhancements, and defect fixes. Feature releases increment the feature release number and are available to the entire on-premises customer base. Feature releases are quarterly.
Cadence: Quarterly
Examples: 11.2.000001, 11.4.000006
Major Version Number
Once a year, a feature release increments the major version number (for example, 11.x to 12.x), marking a significant version milestone. The major version number is essentially a code for the year and is the first digit in the version number.
Cadence: Annually
Examples: 11.2.000001, 11.4.000006
Maintenance Releases
Maintenance releases are issued at Delinea's discretion between feature releases to address defect fixes, security vulnerabilities, or targeted improvements. These releases increment the build number within the current feature release version and are available to the entire on-premises customer base.
Cadence: As needed between feature releases
Examples: 11.3.000049, 11.3.000061, 11.3.000047
Summary
| Deployment | Release Type | Description | Cadence | Version Impact |
|---|---|---|---|---|
| Cloud | Continuous | Features, enhancements, security updates, and fixes delivered via CI/CD. | Ongoing | N/A |
| On-Premises | Feature Release | New functionality, integrations, and enhancements derived from a cloud release. Major version increments annually. | Quarterly | Increments the second digit in the version number. |
| On-Premises | Maintenance Release | Defect fixes, security patches, and targeted improvements | As needed | Increments the third digit in the version number. |
