docs: support versioned docs

[nitrocode]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

• I'd be willing to implement this feature (contributing guide)

Describe the user story

If a pr of a new feature gets merged, the pr would make it into the next release, however the documentation would be updated immediately. This would make it seem like the feature is available in the current version which is not the case.

Describe the solution you'd like

Use versioned docs

See issue

• Docs versioning mechanism vuejs/vuepress#1018

Describe the drawbacks of your solution

More effort which will result in more clarity

Describe alternatives you've considered

Adding the version of each feature as markdown. We do this now every now and then. Sometimes we forget. It's inconsistent.

[Moncky]

Just ran into this. Speficially with the state_rm functionality
https://www.runatlantis.io/docs/using-atlantis.html#atlantis-state-rm which is currently showing on the docs page and is part of the as yet unscheduled 0.23.0 release

[brandon-fryslie]

First of all, love Atlantis, you guys rock. I really appreciate what you're doing.

Here's the problem. It's extremely challenging for Atlantis users to know which features are available. At minimum the flags should say "introduced in version XYZ". I'm using Atlantis for more than "hobbyist" level work which means I can't arbitrarily upgrade to the newest version all the time. Unfortunately it seems like there isn't really a good way to tell what features I can use beyond trying them or reading thru the changelog a few times (which I've done, but not memorized).

I think this would be useful, thanks!

[jamengual]

Totally agree, it will be nice to tight the version to the flag/option, maybe we could at least ask the contributor to add a link to the PR and from there the user can figure out very easily what release was that PR merged into.

…

On Thu, Jul 20, 2023 at 3:50 PM Brandon Fryslie ***@***.***> wrote: First of all, love Atlantis, you guys rock. I really appreciate what you're doing. Here's the problem. It's extremely challenging for Atlantis users to know which features are available. At minimum the flags should say "introduced in version XYZ". I'm using Atlantis for more than "hobbyist" level work which means I can't arbitrarily upgrade to the newest version all the time. Unfortunately it seems like there isn't really a good way to tell what features I can use beyond trying them or reading thru the changelog a few times (which I've done, but not memorized). I think this would be useful, thanks! — Reply to this email directly, view it on GitHub <#3061 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ3EREHUZKUDRNLNGHILHLXRGY2XANCNFSM6AAAAAAUIX35NI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>