Feature Request: Allow for Collection Versioning for Public Documentation in V10

[Postmanaut-Adrian]

Is there an existing request for this feature?

• [X] I have searched the existing issues for this feature request and I know that duplicates will be closed

Is your feature request related to a problem?

In V9, users could tag their collections via the changelog to allow for different versions of their public API documentation.

In V10, this is no longer supported, and now the "Current" version is the only one available unless previous versions were created in V9.

Certain customers need to be able to publish different versions of their documentation as they may be maintaining different versions of their APIs.

Describe the solution you'd like

The customer suggested two things:

1. Enable users to rename the "Current" version to the desired name of their choosing
2. Allow for different versions of a collection to be published and edited.

Describe alternatives you've considered

No response

Additional context

Zendesk Ticket: 140396

[tbhockey]

Thanks for opening this @Postmanaut-Adrian

For us, the specific solution isn't really so important; what we need is a way to publish versioned, public documentation. Pre-v10, this could be achieved through Collection tagging. Post-v10 there doesn't appear to be any way to do this. APIs have nice a nice versioning system, but how to provide versioned documentation for them is unclear, and even then, our understanding is that said API would not be source of public documentation; a Collection is required for public documentation (correct me if I'm wrong).

So if this issue is the best way of providing a solution for what we (and I have to imagine many others) are needing, so be it. I just wanted to clarify that we're open to anything, even if we're just missing something presently available.