Version 2.7
2.7.2 - August 28, 2024
-
Enhancements:
-
Expanded MongoDB Connectivity: You can now connect to external MongoDB databases using both SRV and non-SRV connection strings, offering greater flexibility in your database setup.
-
Improved Embedded Backup and Restore: We enhanced the embedded backup and restore process. Note that this improvement is not available in version 2.8. To benefit from this enhancement, install version 2.7.2 or 2.9.
-
-
Changes:
- Collectd Removed: We removed the Collectd tool from the installation files. If you use Collectd, refer to the Collectd documentation for alternative monitoring solutions.
-
kURL installer:
curl -sSL https://kurl.sh/swaggerhub-2-7-2 | sudo bash
2.7.1 - March 1, 2024
-
Updated VirtServer for security fixes.
-
MongoDB 7 support for external Databases.
2.7 - January 17, 2024
-
Changes to user management:
-
Role-based access control (RBAC) - Admin assigns users appropriate roles. Each role has a set of authorized permissions.
-
Resource-based user access - Roles apply on an Organization, Project, Team, or Resource level.
-
Added the Organizational Role column to the Members table in the Organization Settings page Members tab.
-
Added an option on the Organization Settings page Members tab allowing owners to specify that designers can share resources they can access.
-
Added Team Resource table to the Teams settings page showing a list of all resources (APIs, domains, projects) that the team has been assigned access to.
-
On the Teams settings page, added the ability to add and remove resources.
-
On the Teams settings page, added the ability to toggle team access to specific resources between Designer and Consumer access.
-
Added the ability to assign roles to a project.
-
Updated email notifications:
-
Designers and Consumers will not receive notifications automatically.
-
SwaggerHub team users will receive all notifications for any APIs or domains assigned to the team.
-
-
Changes to user access:
-
Members of Teams are now subscribed to notifications about all resources (APIs, domains, templates) that the teams have access to. Learn how to unsubscribe to notifications here.
-
System-wide permissions have changed, so consumer users may find that their access is more restrictive.
-
If you are a collaborator on APIs or domains in SwaggerHub, the organization associated with those resources will now appear in the left sidebar.
-
-
Changes to user roles and resource access management:
-
Designer and Consumer roles replaced Editor, Viewer, and Commenter roles.
-
Consumers who are members of a team will be upgraded to Designers if the team is added to a resource or project with the Designer role. If there are insufficient Designer license seats available, you will not be able to grant the role change to the team.
-
Updated Member Profile page for adding roles to members.
-
Removed default consumer role assigned to invited users. The invited user now has no default role. After sending the invitation, the organization owner can assign a role to the invited user on the organization’s Member Profile page. Previously invited users were automatically assigned a consumer role.
-
The system-wide option check boxes on the Members page were redone. Users who previously had a consumer role may find that their permissions changed.
-
Notifications about all resources (APIs, domains, templates) available to a team are now sent to every member of the team.
-
Collaborators (users who are not members of teams, with access to specific resources) now appear on the member list in Organization Settings.
-
All icons in the updated access control screens have tooltips, and you can hover over the icon to get a description of the icon’s function.
-
-
Owners can manage invited members ( add them to Teams, Projects, and so on) who didn’t accept the invitation and create an account.
-
Only active accounts take up a license seat.
-
-
Changes to standardization:
-
Standardization rules enabled for AsyncAPI and OpenAPI 3.1.
-
Standardization custom rules now support JSON path expressions.
-
Added an option on the Standardization page for an owner to specify if designers can see Standardization errors in the editor page.
-
Updated Custom Rules for API Standardization.
-
-
Support for OpenAPI 3.1:
-
Catalog support (Search, CRUD).
-
New editor support, including inline documentation of specification items.
-
-
Component updates:
-
Updated Swagger UI to version 5.10.3.
-
Updated Swagger Codegen v2 to version 2.4.37.
-
Updated Swagger Codegen v3 to version 3.0.51.
-
Updated Swagger Client to version 3.24.5.
-
Updated Swagger Editor to version 4.11.2.
-
Updated Swagger Editor Alpha to version 5.0.0-alpha.82.
-
Updated Swagger Core to version 1.6.12.
-
Updated Swagger Core v3 to version 2.2.19.
-
-
Integrations:
- Updated NodeJS 14 and 18 for AWS Lambda plugin.
-
Embedded clusters:
-
Changed Container Storage Interface (CSI) to OpenEBS.
-
Changed Container Network Interface (CNI) to Flannel.
-
Updated Kubernetes to version 1.27.
-
Updated KOTS version to 1.104.
-
-
Existing cluster:
- The minimum required KOTS version is now 1.103.