Version 2.15
2.15.3 - November 2, 2026
Swagger Studio On-Premise 2.15.3 is a security patch release for installations that run 2.15.x. No functional changes and no Helm values changes are expected.
Caution
Critical - Security fix for Node.js vulnerabilities
This release upgrades the Node.js runtime in all Node.js-based On-Premise components to the patched 24.22.x line. It addresses the vulnerabilities published in the Node.js October 2026 security releases. We recommend all customers on 2.15.x upgrade to 2.15.3.
Warning - No backport to 2.14.x and older
The fix is not backported to 2.14.x or older versions. Customers on those versions should upgrade to 2.15.x and then to 2.15.3.
-
What’s New
- Upgraded the Node.js runtime in all Node.js-based On-Premise components to the patched 24.22.x line. For details, see the Node.js October 2026 security releases advisory.
-
Upgrade Notes (2.15.x → 2.15.3):
-
Verify that your installation runs version 2.15.x. If you run 2.14.x or older, upgrade to 2.15.x first.
-
Upgrade to 2.15.3 using your standard Helm upgrade procedure.
-
Confirm that all pods restarted with the new images.
-
2.15.2 - September 11, 2026
This release removes or renames no Helm keys, changes no operator command signatures, and changes no database or hardware requirements. Existing values.yaml files remain valid without modification.
In Release 2.15.2, the bundled Replicated SDK gets fewer permissions. It can now read only the resources it needs, instead of everything in its namespace. The SDK still cannot see outside its namespace, and you do not need to change anything during the upgrade.
-
Deployment and configuration:
-
External secret mounts now reach the maintenance CronJob - Resolved an issue where the maintenance CronJob did not apply the volumes and volume mounts configured for pre-hooks. Deployments that read credentials from an externally mounted secret store, such as a Vault Agent sidecar or a Container Storage Interface (CSI) driver, could not run maintenance operations against those credentials. The maintenance CronJob now mounts the same
extraVolumesandextraVolumeMountsthat you configure underpreHooks, so the scheduled job can access the externally injected secrets at runtime. Pods restart when the mounted credential values change, so the next maintenance run uses the current values.Deployments that configure no extra volumes or mounts are unaffected. The CronJob renders and runs exactly as Swagger Studio On-Premise release 2.15.1.
-
-
Infrastructure updates:
- Replicated SDK runs in minimal RBAC mode - The bundled Replicated SDK now always deploys with minimal Role-based access control (RBAC) mode enabled. By default, the SDK’s namespace Role includes a wildcard rule that grants read access (
get,list,watch) to every resource type in the namespace, which the SDK uses to discover workloads and report their status to Replicated. Minimal RBAC mode replaces that rule with only the permissions the SDK needs: read access to its own deployment and replica set, to pods, and to a small set of named secrets and config maps. Status informers narrow these permissions further to the named resources they cover. Swagger Studio On-Premise behavior remains unchanged. License status reporting and support bundle collection continue to function as they performed in release 2.15.1.
- Replicated SDK runs in minimal RBAC mode - The bundled Replicated SDK now always deploys with minimal Role-based access control (RBAC) mode enabled. By default, the SDK’s namespace Role includes a wildcard rule that grants read access (
-
Helm values updates:
-
Helm values updates - full summary:
Change Key / section Notes Changed preHooks.extraVolumespreHooks.extraVolumeMountsThe maintenance CronJob now receives these volumes and mounts. Removed None No keys removed in this release.
Adjust the volume source to match your secret injection mechanism. The preceding values are illustrative. Use these commented examples in the chart
values.yamlas the authoritative reference for your setup.Example: Externally injected secret volume
global: secrets: injectedVolume: name: vault-secrets mountPath: /etc/swaggerhub/secrets volume: emptyDir: medium: MemoryExample: pre-hook mounts applied to the maintenance CronJob
preHooks: extraVolumes: - name: vault-secrets emptyDir: medium: Memory extraVolumeMounts: - name: vault-secrets mountPath: /etc/swaggerhub/secrets readOnly: true -
-
Upgrade notes (2.15.1 → 2.15.2):
-
Back up the database and your current
values.yamlfile. -
Confirm that you are upgrading from 2.15.1. This release requires no changes to
values.yaml. -
Upgrade Swagger Studio On-Premise to release 2.15.2 using your usual method, which is the KOTS admin console for online installations, or the airgap bundle for disconnected environments.
-
If you are using an external secret injection, render the chart and confirm that the maintenance CronJob manifest includes your configured volumes and mounts.
-
Optionally, verify that the Replicated SDK’s Role no longer contains the wildcard rule. List the RBAC objects in the release namespace, and then inspect the SDK’s Role as follows:
No manual cleanup is needed. The upgrade updates the Role in place.
kubectl -n <namespace> get role,rolebinding | grep -i replicated kubectl -n <namespace> get role <replicated-role> -o yaml -
Confirm that the Replicated SDK pod is running and reporting license status correctly.
-
Run a smoke test that covers sign-in, SSO, the editor, the registry, integrations, and Portal.
-
Run the maintenance CronJob manually, or wait for the next scheduled run. Confirm from the logs that it completes without authentication errors.
-
2.15.1 - September 3, 2026
Kubernetes 1.31 and 1.32 are no longer supported. The supported Kubernetes range for 2.15.1 is 1.33 to 1.36, and the Helm chart now declares a minimum Kubernetes version of 1.33.0. The chart rejects installation and upgrade on an unsupported cluster version.
Upgrade your cluster to Kubernetes 1.33 or later before you upgrade Swagger Studio On-Premise. We recommend running the most recent version in the supported range.
The minimum KOTS version is now 1.130.5, raised from 1.128.0 in 2.15.0. The newer KOTS version is what makes Kubernetes 1.36 support possible.
Update the KOTS CLI and the Admin Console to 1.130.5 or later before you deploy 2.15.1. The embedded cluster (kURL) installer bundle for this release ships Kubernetes 1.34.
Version 2.15.1 reinstates the Bitbucket Server integration, but the integration remains deprecated and unsupported. Plan a migration to a supported alternative, as the integration may be removed in a future release.
-
Deployment and configuration:
-
LDAP domain search password from an external secret - You can now supply the password used for LDAP domain search the same way as the other managed credentials, either from a file on disk or from an external secret store such as External Secrets Operator with Vault. Two new Helm values are available:
global.secrets.localPath.ldapPasswordfor the file path, andglobal.secrets.secretKeys.ldapPasswordKeyfor the external secret key. This removes the need to patchvalues.yamlby hand in GitOps-managed, Helm-only deployments. -
Volumes and volume mounts for hook jobs - Pre-hook and post-hook jobs now accept their own
extraVolumesandextraVolumeMountsdefinitions. This makes file-based secret mounting work end to end for the hook jobs, which previously could not be given a volume separate from the application services. TheextraVolumesdescriptions are also clarified across all components, andglobal.secrets.localPathnow documents the expected volume-mount pattern.
-
-
Integrations:
- Bitbucket Server integration reinstated - Fixed issue where the Bitbucket Server integration was hidden for all on-premise users after upgrading to 2.15, including organizations that had already configured it. Version 2.15.1 reinstates the integration so the existing configurations continue to work, while the integration remains deprecated.
-
Editor, comments, and API:
-
Features that rely on secure browser APIs now work over HTTP - Fixed issue where several actions failed silently on instances served over plain
http://rather than HTTPS, because the browser exposes the underlying APIs only in a secure context. Replying to an editor comment, copying a request or response from the Try it out tab, and in-application notifications are all affected, and now work on instances served over HTTP. Serving Swagger Studio over HTTPS remains the recommended configuration. -
Domain endpoints aligned with the published OpenAPI definition - This release resolves a number of mismatches between the Registry API domain endpoints and their published OpenAPI definition. Invalid request bodies and unsupported content types now return the documented client-error responses instead of a server error, existence and authorization checks run in a consistent order, and endpoints that require an internal service token are documented as such. If your automation depends on the previous status codes, review it against the updated definition.
-
-
Cluster component updates:
-
Updated the supported Kubernetes range to 1.33 through 1.36.
-
Updated the minimum KOTS version to: 1.130.5.
-
The kURL installer bundle for this release ships Kubernetes 1.34.
-
-
Helm values updates:
-
LDAP domain search password - A new block under
global.secretssupplies the LDAP domain search password from a file path or an external secret key, matching the pattern used for the other managed credentials.global: secrets: localPath: # -- File path for the LDAP domain search password. ldapPassword: "" secretKeys: # -- External secret key for the LDAP domain search password. ldapPasswordKey: "" -
Hook job volumes -
preHooksandpostHookseach accept their ownextraVolumesandextraVolumeMountsdefinitions, using the same schema as the existingextraVolumessupport for other components. -
Helm values updates - full summary:
No keys are removed or renamed in this release.
Change Key / section Notes Added global.secrets.localPath.ldapPasswordFile path for the LDAP domain search password. Added global.secrets.secretKeys.ldapPasswordKeyExternal secret key for the LDAP password. Added preHooks.extraVolumes/preHooks.extraVolumeMountsMount volumes, for example secrets, into pre-hook jobs. Added postHooks.extraVolumes/postHooks.extraVolumeMountsThe same capability for post-hook jobs. Changed global.secrets.localPathDescription updated to cover LDAP and clarify the volume-mount pattern. Changed extraVolumes(all components)Description clarified. Behavior is unchanged.
-
-
Upgrade notes (2.15.0 → 2.15.1):
-
Confirm your Kubernetes version. Your cluster must run a version in the 1.33 to 1.36 range. If it does not, upgrade the cluster before you upgrade Swagger Studio On-Premise. Run the most recent version in the supported range when possible.
-
Update KOTS. (KOTS installations only.) Update the KOTS CLI and the Admin Console to version 1.130.5 or later.
-
Back up your instance. Take a full backup, including external MongoDB and PostgreSQL databases if you use them.
-
Review Helm values. Compare your
values.yamlfile against the Helm values updates above. This release removes no existing keys, so no edits are mandatory. -
Configure the LDAP secret. (Optional.) If you manage credentials through an external secret store and want the LDAP domain search password included, add
global.secrets.secretKeys.ldapPasswordKeyto your configuration. For file-based secrets, addglobal.secrets.localPath.ldapPasswordinstead. -
Deploy 2.15.1. Verify that all services reach a ready state.
-
Verify authentication. If you use LDAP, confirm that a domain search still succeeds.
-
Confirm the Bitbucket Server integration. If your organization uses it, confirm it is visible again and begin planning a migration to a supported alternative.
-
2.15 - June 25, 2026
Caution
Important upgrade prerequisites:
-
KOTS installations - Ensure you are running 2.13.x or higher before upgrading to 2.15.
-
Helm installations - Ensure you are running 2.14.x before upgrading to 2.15.
-
Integrations:
-
Signed commits for GitHub Sync - Swagger Studio On-Premise now supports signed commits for GitHub Sync integrations. With this feature enabled, Swagger Studio cryptographically signs all commits pushed to GitHub with an organization-level SSH key, and they appear as Verified in your repository’s commit history. This satisfies branch protection rules and signed-commit policies enforced by enterprise GitHub configurations.
The feature is disabled by default and is enabled through Helm values. See GitHub Sync for configuration details.
-
-
SSO and user management:
-
SAML AuthnRequest signing - Swagger Studio On-Premise can now sign outbound SAML AuthnRequests sent to your Identity Provider, satisfying IdP configurations that require a verified Service Provider identity, such as enterprise WebSSO systems that reject unsigned authentication requests. Signing is disabled by default. When enabled, the application can auto-generate a self-signed certificate and key, or use a certificate and key that you supply.
Your existing SAML configuration is unaffected. The
idpCertificatefield used to verify IdP-signed assertions remains unchanged. SAML AuthnRequest signing is a separate, additive capability that you configure undersettings.auth.saml.requestSigning. -
Team management across organizations - The on-premise administrator no longer needs organization membership to manage teams through the User Management API, and can call team management endpoints for any organization. This change aligns team API permissions with existing admin privileges for other resource types.
-
-
Helm values updates:
-
Signed commits configuration - A new top-level block under
settingscontrols the signed commits feature for GitHub Sync integrations. To enable signed commits, add thesettings.signedCommitsblock and setenabled: true, then provide the committer identity and SSH private key.settings: # -- Configure signed commits feature for Swagger Studio On-Prem users. # Allows cryptographically signing commits sent via GitHub Sync integration. signedCommits: # -- Enable signed commits for GitHub SCM integrations. enabled: false # -- Username of the GitHub account used as the commit signer. committerUsername: "" # -- Email address of the GitHub account used as the commit signer. committerEmail: "" # -- Private SSH key used to sign commits. Keep this value secret. privateSshSigningKey: ""Keep the
privateSshSigningKeyvalue confidential. Provide the private key through a Kubernetes Secret or an external secrets manager rather than committing it in plain text. -
SAML AuthnRequest signing - A new block under the existing SAML configuration enables SP-side signing of SAML AuthnRequests. By default,
generateCert: truecauses the application to auto-generate and persist a self-signed keypair in a Kubernetes Secret. SetgenerateCert: falseand provide your own certificate andprivateKeyif your IdP requires a specific SP certificate.settings: auth: saml: requestSigning: # -- Enable signing of SAML AuthnRequests sent to the Identity Provider. enabled: false # -- Automatically generate a self-signed certificate and private key for request signing. # Set to false to provide your own certificate and key via the fields below. generateCert: true # -- PEM-encoded X.509 certificate used to sign SAML requests. # Only used when generateCert is false. certificate: "" # -- PEM-encoded private key corresponding to the certificate above. # Only used when generateCert is false. privateKey: "" # -- Signing algorithm. Supported values: sha256, sha512. algorithm: "sha256" -
Helm values updates - full summary:
Change Key / section Notes Added settings.signedCommits.*Controls signed-commit feature for GitHub Sync integrations (disabled by default). Added settings.auth.saml.requestSigning.*Controls SP-side SAML AuthnRequest signing, including auto-generation of the SP keypair (disabled by default).
-
-
****Maintenance operation command updates:
- The new
grant-admin-orgs-ownershipcommand assigns an owner role to the admin user in every organization where they do not already have that role. This command replaces a previous maintenance script and provides a supported, in-product solution.
- The new
-
Miscellaneous:
-
Backup and restore operations no longer invalidate active user sessions. In earlier releases, running the
backupandrestoreoperator commands invalidated authentication tokens, leading to errors. The restore process now signs you out gracefully. -
GitHub sign-in now correctly redirects new users to Swagger Studio home page after registration. Previously, signing up through GitHub sent users to an incorrect welcome page.
-
The options to link or unlink your Swagger Studio account to GitHub are no longer visible on your profile page. These actions were non-functional after a previous release removed the backend endpoints they relied on. To prevent confusion, these options no longer appear.
-
The home page now displays correctly at standard laptop resolutions. Previously, users could experience rendering issues at certain resolutions, such as the default MacBook display at 1496 × 967 pixels. The layout is now fully responsive.
-
Various stability and security fixes.
-
-
Component updates:
-
Updated K8s to version: 1.34.
-
Updated KOTS to version: 1.130.4.
-
Updated Swagger Editor to version: 5.6.1.
-
Updated Swagger Core v3 to version: 2.2.50.
-
Updated Virtserver to version: 3.32.0.
-
-
Upgrade notes (2.14.x → 2.15.0):
-
Review and update Helm values. Add the new
settings.signedCommitsblock, thesettings.auth.saml.requestSigningblock, or both, depending on which features you intend to enable. This release removes no existing keys. For the exact YAML blocks to add, refer to Helm values updates above. -
Configure signed commits. (Optional.) If your GitHub branch protection rules require verified commits, generate an SSH key pair, add the public key as a signing key on your GitHub committer account, and configure
settings.signedCommitsin your values file. Provide the private key through a Kubernetes Secret or an external secrets manager. Do not commit it in plain text. -
Configure SAML AuthnRequest signing. (Optional.) If your identity provider (IdP) requires signed AuthnRequests, set
settings.auth.saml.requestSigning.enabled: true. You can usegenerateCert: trueto automatically generate a self-signed key pair, or provide your own certificate and key. Share the service provider (SP) public certificate with your IdP team to complete trust configuration. -
Update automation that uses operator commands. Configure any scripts, runbooks, or other automation to call the
grant-admin-orgs-ownershipoperator command. Run it with--dry-runfirst to preview the scope of changes. -
Run preflight checks. Execute the preflight checks provided in the installer to validate environment readiness before the upgrade.
-