Rule docs on website should show the latest version, not what's in the main branch

[sindresorhus]

Before You File a Documentation Request Please Confirm You Have Done The Following...

• I have looked for existing open or closed documentation requests that match my proposal.
• I have read the FAQ and my problem is not listed.

Suggested Changes

I wasted a lot of time now because I thought the fixStyles option for the consistent-type-imports rule here was available in the latest release since it's shown on the website: https://typescript-eslint.io/rules/consistent-type-imports/#fixstyle

It's expected that a website shows docs for the latest available release, not what's in the main branch.

Affected URL(s)

https://typescript-eslint.io/rules/

[lsagetlethias]

Same as the playground that should not used the main branch but the last release. (eslint playground)
Really confusing.

[Josh-Cena]

The release script is not public, so I'm going to let @JoshuaKGoldberg do it. Basically we just need to run yarn docs:version during release.

[JoshuaKGoldberg]

I'm working on this now. Plan is to:

1. Short term: have Netlify pull from a docs website branch that's only updated on releases
2. Long term: look into Docusaurus versioning or a similar system
   • Edit: Website: should we keep docs of old versions available? #6056

[JoshuaKGoldberg]

Ok, the website should be pinned to the latest stable released version now. #6055 will add an explicit version number to it too, but this issue is technically resolved. So I'll close it now.

Thanks for posting @sindresorhus, @lsagetlethias, and everyone who 👍d! Please let us know in new issues if there are any other website bugs or features you'd like to see. ❤️