chore: docusaurus deploy version v28.1.0

[github-actions]

No description provided.

[julienrbrt]

Do we really need a whole new doc deployment per minor / patch release?

Imho it could just be major based.

[github-actions]

Visit the preview URL for this PR (updated for commit 7a7c407):

https://igntservices-docs--pr3864-chore-docs-new-versi-fe0kdij3.web.app

_{(expires Sat, 13 Jan 2024 04:59:02 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 95379efd94dd497aaa37c2d0354e6e2cafca5ec5}

[jeronimoalbi]

Do we really need a whole new doc deployment per minor / patch release?

Imho it could just be major based.

I think it would make sense for major and minor but we should remove the patch number from the versions selector if possible to avoid confusion. Also in the docs we could refer to version as just vX.Y.

Depends on how we move forward but I guess minor releases might include migrations that should be documented so they would need updating the docs.

[julienrbrt]

Depends on how we move forward but I guess minor releases might include migrations that should be documented so they would need updating the docs.

I'd argue that you should always use the latest of a major (like it was assumed you would always the latest of v0.x.x).
If there are documentation changes, we can probably just update it directly?