The spec itself doesn’t address versioning. The spec is intended as one root per API.
Now, what’s an API? A specific version? Multiple ones? That’s your call. I’d probably use a different spec file for each version. From: <[email protected]> on behalf of Denis <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, 8 December 2016 at 8:19 To: Swagger <[email protected]> Subject: API versioning support Hi guys We've created some sort of API. And API has versioning support like: localhost/v1/member and localhost/v2/member etc. My question is... Does Swagger have some special support for different versions of API? Or maybe, do we need to deploy for each API version separate instance of Swagger UI simply? -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
