Closed philippeluickx closed 6 years ago
As reference, the Swagger UI upgrade task is here:
https://github.com/apinf/api-umbrella-dashboard/issues/1363
Also related, Swagger UI is now at version 2.2.0, so we may need to upgrade again soon.
One other thing to note, it may not have been the Swagger UI upgrade that caused the bug.
Rather, we had changed our swagger file identification pattern. This change was bundled with our 0.2.28 release, breaking backwards compatibility with previous swagger file IDs.
See bug report #1409 for a description of the routing changes, and plans for a fix. See also #1375 for plans to preserve backwards compatibility, to the extent possible, through database migrations.
After the latest Swagger-UI update, some Swagger files for a client implementation broke. We need to make sure that all OS components we use are working nicely together. We should test with real-life test data.
Might also be a good idea to analyze and include changelogs from these components in our releases of apinf, e.g. https://github.com/swagger-api/swagger-ui/releases