Swagger Studio On-Premise Release Notes
Before you upgrade: read the upgrade notices (VirtServer license expiry, Bitnami catalog changes).
Looking for Swagger Studio SaaS release notes? See here.
This page contains a list of new features and other changes introduced with each release of Swagger Studio On-Premise.
⇒ 1.x customers, learn about:
⇒ 2.x customers, learn about:
- How to upgrade 2.x instances
Latest version (fully supported)
The latest release is described below. If you are still running a 1.x release, click on the 1.x tab for the latest updates. If you don’t know how to determine your current version, click here.
Important upgrade notes
Always make sure you are running the latest release version. Depending on your current setup, the following may apply:
-
Versions earlier than 2.7 - An upgrade to the latest release is required due to issues with Longhorn that affect older versions.
-
Versions 2.4.1 and older 2.x VM installs with internal databases - You must first upgrade to 2.6.1 before proceeding to 2.7.1. This does not affect customers migrating from 1.x, as specified in Migrating from SwaggerHub on-Premise 1.x to 2.x.
-
Upgrading to 2.7 - Certain team settings may impact the designer license type usage after upgrading to 2.7. To find out more, see 2.7 Migration Impact on Licenses.
-
Upgrading a VM installation - This process involves significant component upgrades and requires additional manual steps before and during the installation. Refer to Upgrading KOTS for details.
Release notes by version
- Version 2.16
- Version 2.15
- Version 2.14
- Version 2.13
- Version 2.12
- Version 2.11
- Version 2.10
- Version 2.9
- Version 2.8
- Version 2.7
- Version 2.6
- Version 2.5
End-of-life versions (2.0 to 2.4 and 1.x): see here. Support status of each version: Support Policy.