--- title: "Software Release Information for Service Upgrades" slug: "software-release-information-for-service-upgrades" description: "Graphiant's Software Release Life Cycle ensures continuous delivery of stable upgrades, featuring Latest, Recommended, and Stable Releases for optimal performance." updated: 2026-05-11T19:51:56Z published: 2026-05-11T19:51:56Z canonical: "docs.graphiant.com/software-release-information-for-service-upgrades" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.graphiant.com/llms.txt > Use this file to discover all available pages before exploring further. # Software Release Information for Service Upgrades ## Graphiant's Software Release Life Cycle Graphiant employs a rolling release cadence for software upgrades. Continuous delivery of software releases provides not only the stability from building upon prior versions, but also the added benefit of simultaneously delivering new features, including within the data plane. This process ensures features and fixes at a quick cadence with high quality. Support overlap of the preceding release is maintained, to ensure that you may upgrade at your convenience. ### Supported Releases: #### Latest Release: The Latest software release is the most current version, containing the newest features. **A Latest Release is:** - Released every month, and is a short-term release. - Supported for: - First month: Critical bug-fixes - The following 45 days: Spot-fixes - Actively tested in QA while it is supported; it will not be in QA after that. #### Recommended Release: Every 3rd Latest Release is targeted to be the Recommended Release, which provides a version that has had continual development and bug-fixes for one month prior to earning the title of Recommended. **A Recommended Release is:** - Released every three months. - Supported for: - First three months: Active critical fixes - The following 3-1/2 months: Spot-fixes - Actively tested in QA while it is supported; it will not be in QA after that time. #### Stable Release: Every 4th Recommended Release is targeted to be the Stable Release, which provides a version that has continual development and bug-fixes for twelve months. **A Stable Release is:** - Released every 12 months, and is a long-term release. - Supported for: - First six months: Active critical fixes - The following six months: Spot-fixes - Actively tested in QA while it is supported; it will not be in QA after that time. #### Software Release Table | **Release Type** | *Latest* | *Recommended* | ***Stable*** | | --- | --- | --- | --- | | **How Frequently Released** | Every month | Every three months | Every twelve months | | **Length of Support** | 2-1/2 months | 6-1/2 months | Twelve months | | **Ideal Use** | Newest features | Prolonged Use | Prolonged Use | > [!NOTE] > Once a software release has been deployed: > > - Images will keep changing, but only with critical bug-fixes in a given release train. > - Any non-critical bug-fixes are only available in the next release. > - Any added features and large changes will also be available in the next release, so as to not impact baseline stability. > [!NOTE] > Should a bug-fix need to occur prior to the next release: > > - A Maintenance Release will be deployed. > - Upgrade to this Maintenance release to be ensured of the most reliable image. ### Release Nomenclature Graphiant uses the YY.MM. methodology of naming software versions, where: - YY = Last 2 digits of the year that the software version was released - M / MM = Month that the software version was released. - = placeholder for which number release the version is within it's release train. For example, a software release built in March 2025 that is the 2nd version would be named 25.3.2. Likewise, in general the naming convention for any version within a release train in December of 2025 would be 25.12.x. For any Maintenance Release, the release will end in one number greater than the prior-deployed version within that release train. For example, if the current Latest version is 25.6.1 and a bug-fix occurs prompting a Maintenance Release, it would be labeled 25.6.2. ### Software Release Life Cycle Chart ![Timeline of software releases with critical bug-fixes and support details for each version.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Software LifeCycle 2026.png) This image represents the rolling cadence of Graphiant's Software Release Life Cycle. - A new Latest Release is offered every month, ideal for keeping up with the latest features. - The Recommended Releases are offered every three months. Since these releases are supported in their entirety for 6 months, they are ideal for prolonged use. - The Stable Releases are offered every twelve months. Since these releases are supported in their entirety for 12 months, they are ideal for environments that require the slowest possible upgrade cycle. - Support overlap of the preceding release ensures that you may upgrade at your convenience. > [!NOTE] > Note: > > - At any given time, a Latest Release, Recommended Release and Stable Release are available from which to choose. > - Please review the Release Notes for Stable, Recommended and Latest to determine the release that best works for your environment. For any questions, please reach out to [Customer Support](https://support.graphiant.com/hc/en-us/requests/new) and/or your Sales Engineer and we can provide further guidance. For information on the End of Maintenance / End of Life for each software release, click [here](https://docs.graphiant.com/docs/software-end-of-maintenance-and-end-of-life-information). ## The Graphiant Continuous Integration / Continuous Delivery (CI/CD) Process Graphiant not only maintains baseline stability, but also improves it - with new features and remediating bugs along the way that exist in the currently deployed images. Graphiant heavily relies on automation in all stages of the continuous integration / continuous delivery process, in both in testing and operations, to ensure the avoidance of regressions while still maintaining a quick cadence of stable new features. The journey of CI/CD starts with the Developer-Managed Stages, and is followed by the QA-Managed Stages. Within this process Graphiant performs many tests, at both the developer and QA levels, to ensure high-quality features and releases. ![](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/image(370).png) ## Should an Issue Arise After Upgrading Occasionally issues may occur and those are handled with the same high quality of support that Graphiant offers in every facet of the CI/CD process. Should a key failure case occur, automation assists whenever possible in a quick rollback. Graphiant shares this data within the Release Notes in the interest of transparency, and commitment to quality services and quick resolution of issues. > [!NOTE] > Note: > > - This would not include bugs in new features, nor bugs in old features that were not seen before. > - Not upgrading to new releases will inevitably lead to hitting prior found and fixed issues, more so than seeing new ones. ## Notification of New Releases When Graphiant releases a new software version, a purple banner will appear at the top of the screen upon login to the Graphiant Portal. ![Dashboard displaying usage statistics, services, and quick access options for users.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/New Release Banner full screen Purple 0925.jpg) From here you can click **‘View Release Notes'** and see the versions introduced and what features they have. ![Announcement of a new Graphiant release with a link to view release notes.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/New Release purple banner 'View Release Notes'.jpg) Here you will find the information on the new releases. ![](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/image(374).png) ## Scheduling a Manual Upgrade of Your Graphiant Device Should you want to manually upgrade your device, **click on the ellipses** to the right of that device; **select ‘Schedule Manual Upgrade’**. ![Device lifecycle management interface showing upgrade statuses and options for devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle Devices tab 3 dots 'Schedule Manual Upgrade'.jpg) Alternatively, if multiple devices are selected, the actions are listed at the top of the table. **Select ‘Schedule Manual Upgrade’.** ![Device lifecycle management interface showing upgrade options and device statuses.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle mult Edges 'Schedule Manual Upgrade' at top(1).jpg) This will open a modal to customize your upgrade. Fill out the following fields: - **Upgrade Type:** - ***Download and Install:*** Install the software to your device as well as have a copy downloaded - ***Download Only:*** Download the software, install at a later date - **Upgrade Timing:** - ***Now:*** The upgrade will happen immediately - ***Later:*** The upgrade will be scheduled for a future time and date in a calendar that will appear here - **Select Version:** - ***Recommended:*** The software that is released every 3 months, after having been utilized and tested for three months prior. See more information on [Recommended Releases](https://docs.graphiant.com/docs/software-release-information-for-service-upgrades#recommended-release). - ***Latest:*** The software version that is released every month with the most recent features. See more information on [Latest Releases](https://docs.graphiant.com/docs/software-release-information-for-service-upgrades#latest-release). ![Options for scheduling a software upgrade, including timing and version selection.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle Upgrade modal fields highlighted.jpg) Once you have filled in the desired information, **click ‘Schedule Upgrade’**. ![Schedule a manual software upgrade by selecting options for timing and version.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle upgrade modal 'Schedule Upgrade'.jpg) ### Software Upgrade Scheduled for “Now” If you selected “Now” for your upgrade, the device will immediately start the process. While the software is upgrading, the device will be put in Maintenance Mode, and the status will read “Upgrade in Progress”. ![Device lifecycle management showing upgrade status and maintenance for various devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle Update in Progress.jpg) When complete, the device will have a status of “Up to Date” in the Device table. ![Device lifecycle management table showing upgrade status and active devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle Up to Date in table after Upgrade.jpg) ### Software Upgrade Scheduled for “Later” If you selected “Later” for your upgrade, the device will show an Upgrade Status of “Upgrade Scheduled”. ![Device lifecycle management showing upgrade status and software versions for various devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle 'Upgrade Scheduled'(1).jpg) Upon hover, you will see: - The Release Train of the software to be installed upon upgrade - The software Version that will be installed - The date & time that the upgrade will occur ![Software upgrade status showing scheduled and available updates with version details.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle Scheduled Upgrade info on hover.jpg) ## Performing Rollback to the Previous Software Version If your device has the Status of “Up to Date” you can roll back to the prior version of software. > [!NOTE] > Note: > > You can only roll back to the software version that was immediately prior to the current software. > > Devices that have a Status of “Upgrade Available” will not have this option. **Click the ellipses; select ‘Rollback to Previous Version’.** ![Device lifecycle management table showing upgrade statuses and actions for various devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle 3 dots 'Rollback to Previous Version'(1).jpg) A modal will appear confirming the rollback intention, and that a brief service interruption may be experienced during the process. **Click ‘Rollback Devices’.** ![Confirmation prompt for rolling back a device to a previous software version.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/'Device Lifecycle Rollback modal warning 'Rollback Devices;.jpg) While the rollback is in progress, the device will automatically be put into Maintenance Mode. ![Device lifecycle management showing upgrade status and maintenance for various devices.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle Rollback 'Upgrade in Progress' and in Maint Mode.jpg) The device will now be back on the prior software version, and out of Maintenance Mode. > [!NOTE] > Note: > > You can upgrade again at any time. ![Device lifecycle management showing upgrade status and active devices in a table format.](https://cdn.document360.io/d86ecd1c-49f6-4fac-83cc-5e344f28f84f/Images/Documentation/Device Lifecycle after rollback for Doc360 to recognize.jpg) ## Graphiant Recommended Device Upgrade Order Graphiant recommends upgrading network devices in the following order: - **1) High-Availability Deployments:** - If configured for Active / Backup, upgrade the Backup device. - If configured for Active / Active, upgrade the "B" device. - **2) Non-HA Deployments, Single Edge Sites with low traffic / users.** - **3) High-Availability Deployments:** - If configured for Active / Backup, upgrade the Active device. - If configured for Active / Active, upgrade the "A" device. - **4) All remaining Non-HA Deployments, Single Edge Sites with high traffic / users.** > [!NOTE] > Batch Size: > > Graphiant recommends a batch size of fifteen devices for simultaneous upgrade, but no more than twenty-five.