Skip to main content
Swagger
All documentation pages

Version 2.16

2.16.1 - November 10, 2026

Swagger Studio On-Premise 2.16.1 is a security patch release for installations that run 2.16.0. It makes no functional changes.

Caution

Security fix for VirtServer and Swagger Generator

This release fixes security vulnerabilities in VirtServer and Swagger Generator. Customers on 2.16.0 should upgrade to 2.16.1.

This release removes or renames no Helm keys and changes no operator command signatures. Apart from the image tags, you don’t need to change your values.yaml file.

  • What’s New

    • Swagger Generator upgraded - Updated Swagger Generator from version 3.0.83 to 3.0.85 with security fixes.

    • VirtServer upgraded - Updated VirtServer from version 3.34.0 to 3.35.0-fix.1 with security fixes.

  • Upgrade Notes (2.16.0 → 2.16.1):

    1. Verify that your installation runs version 2.16.0. If you run an earlier version, upgrade to 2.16.0 first.

    2. Upgrade Swagger Studio On-Premise to release 2.16.1 using your usual method: the KOTS admin console for online installations or the airgap bundle for disconnected environments.

    3. Verify that all services reach a ready state.

2.16.0 - November 5, 2026

Caution

Important upgrade prerequisites:

  • KOTS and Helm installations - You can upgrade to 2.16 directly from 2.14.x or later.

This release doesn’t remove or rename any Helm keys and doesn’t change any operator command signatures.

  • Editor:

    • gRPC protocol support (read-only) - You can now import a single-file Proto3 .proto file into Swagger Studio and view it in a dedicated gRPC view. The view lists services, methods, messages, and enums, and marks streaming methods with a badge. To refresh the definition, select Re-import this file.

    • Model Context Protocol (MCP) definition support - You can now create and edit MCP definitions, including Tools, Resources, Resource Templates, and Prompts. The editor validates the JSON live as you type.

    • Faster Swagger UI rendering for large API definitions - Swagger UI now renders only the operations and schemas that are visible on screen, which improves responsiveness for large API definitions.

    • Collaboration conflict resolution - When you save an API and another user has saved changes in the meantime, the editor now lets you keep your changes, compare them with the saved version in the diff viewer, or discard your draft. For domains, the diff viewer isn’t available.

    • Download definitions as flattened or non-flattened - You can now download an OpenAPI 2.0 or 3.0 definition as a flattened file, with references resolved, or as a non-flattened file.

  • Governance:

    • Project-level style guides - Swagger Studio now shows an indicator when an API, Domain, or Template is associated with a single project, so you can see which project-level style guide applies.

    • Spectral ruleset editor: Try it out and validation panel - The Spectral ruleset editor now includes a Try it out feature and a validation panel. You can test a ruleset against sample content and see the results right away, without publishing the ruleset first.

    • Style guide badges with counts - Swagger Studio now shows badges with counts for style guide results, so you can see governance findings at a glance.

  • Portal:

    • Custom CSS in Portal configuration - Portal administrators can now add custom CSS in the Portal configuration to match the portal’s appearance to their branding.

    • HTML support in the portal footer - Introduced in version 2.14, the portal footer now accepts full HTML. Administrators can use HTML to format links and legal text.

  • Security:

    • Server-side request forgery (SSRF) protection for webhook integrations - Webhook integrations now include additional protection against SSRF.

    • This release includes stability and security fixes.

  • Architecture changes:

    • PostgreSQL storage for comments, drafts, and preferences - Swagger Studio now stores editor comments, drafts, and preferences in PostgreSQL instead of MongoDB. This change is part of the ongoing effort to remove MongoDB as a dependency.
  • Component updates:

    • Updated OpenSearch to version 3.8. This version uses a security-hardened Docker Hardened Images (DHI) base image.

    • Added support for external MongoDB 8.3.

    • Updated Kubernetes in the embedded cluster (kURL) to version 1.36.

    • Updated KOTS in the embedded cluster (kURL) to version 1.132.0.

  • Supported versions (2.16):

    Component Embedded cluster (kURL) Existing cluster Internal databases External databases
    Kubernetes 1.36 1.33, 1.34, 1.35, 1.36 - -
    KOTS 1.132.0 1.130.5 or later - -
    Velero 1.16.2 1.6.x through 1.16.x - -
    OpenShift - 4.20 - -
    PostgreSQL - - 14.18 14 to 18
    MongoDB - - 8.0 6.0, 7.0, 8.0, 8.1, 8.2, 8.3
  • Fixes:

    • Resolved an issue where Swagger Studio froze when you opened a specific large OpenAPI definition.

    • Resolved an issue where the totalCount value differed between the API Designer and API Consumer views.

    • Resolved an issue where conflicting roles inherited from teams on Portal products were set to the Consumer role instead of the Designer role.

    • Resolved an issue with the output folder issue in the Git integration panel.

  • Upgrade notes (2.14.x or later → 2.16):

    1. Before you upgrade, back up your instance, including any external MongoDB and PostgreSQL databases. This release moves comments, drafts, and preferences from MongoDB to PostgreSQL.

    2. Before you upgrade, back up your values.yaml file. This release doesn’t remove or rename any existing keys, so you don’t need to edit the file.

    3. Upgrade Swagger Studio On-Premise to release version 2.16 using your usual method. For online installations, use the KOTS admin console. For disconnected environments, use the airgap bundle.

    4. After the upgrade finishes, confirm that all services are ready.

    5. After you upgrade, review the targets of your configured webhooks to confirm they still work with the additional SSRF protection.

Was this page helpful?