[Changelog] v4.9.0


(Taylor Barnett) #1

Stoplight v4.9.0 Release

Release files on GitHub

New :rocket:


Users can now interact with OpenAPI Specification extensions through the Stoplight visual editor. Extensions are reusable components that describe additional functionality beyond what is covered in the OpenAPI Specification. They are generally vendor specific, such as Amazon API Gateways extension. All OpenAPI extensions begin with x-. Read more on how to use extensions in the docs here.

Enhancements :muscle:

  • [Modeling] Added ability to support ‘no security’ for an API operation
  • [Modeling] Added a banner letting users know they can’t edit without write access
  • [Hubs] Removed endpoints marked private from the specification document when download link is selected
  • [Modeling] Added safeguard for scopes, specifically with OAuth

Fixes :wrench:

  • [Hubs] Markdown code blocks were not getting highlighted
  • [Hubs] When you changed pages, they were being replaced in the body frame without resetting scrolling to the top of new page (Forum Link)
  • [Mocking] Unable to enter a forward-slash character in path for mock test request
  • [Modeling] - Changing an object to any of the combination types (allOf, anyOf, oneOf) erases the data
  • [Hubs] Variable templating was not working properly in Hubs
  • [Hubs] Path Parameter Variables were not showing in Test Request UI when both http and https were set as security schemas (Forum Link)
  • [Platform] Editor sometimes showed warnings that someone else was editing when they were not

(Thomas De Groof) #2

Since updating to the 4.9.0, we’ve encountered a lot of crashes in the Read mode of the Modeling part.

Steps to reproduce

  1. Open a modeling file in Read mode
  2. Click on an endpoint in the sidebar navigation

Excepted behavior
The endpoint details are shown.

Actual behavior
Error modal “Darn! Something went wrong” with reload button.
After reload the endpoint is correctly shown.
The error repeats when clicking on another endpoint.

Console error:

(Taylor Barnett) #3

Hey @thomas.degroof, that’s no good. Are you using only seeing this in the desktop app or also in the web app?

(Taylor Barnett) #4

We have a fix going out for this very soon! Only was happening on desktop apps, not web.

(Thomas De Groof) #5

Desktop app only, confirmed!
When is very “soon”? :wink:

(Brian) #6


That release should be early tomorrow morning.