Published docs use main instead of released version about baybe

[AdrianSosic]

Hi @monken, in fact the current situation is even worse: the online version has temporarily been built via a manual workflow trigger, so it's even desynced from main. The problem is that we have no multiversion docs in place yet, and you are not the first one to run into this. I've kept pushing for this feature several times but the priority doesn't resonate as much in the team ...

@Scienfitz @AVHopp: Having a main page whose primary example doesn't work is really terrible 🙈 Given that @monken is now the nth person running into this issue and we'll always tap into other issues in the future, I'm absolutely for fixing this next week. Let's talk in the dev meeting how to handle it 🤓

[Scienfitz]

In this case we can easily identify the culprit :)

We should finish the remaining things for 0.9.0 which imo we are 70-80% through with the development. This would resync the page too.

We could also republish the 0.8.2 version of the docs in the meantime.

I agree that the docs should finally be versioned asap, but imo no need to interfere 0.9.0 development for that, lets do it immediately afterwards

[AVHopp]

Then I'll start working on all of the stuff necessary for this asap, and will already start necessary preparations.
Two things in the mean time:

• Yes, we should definitely just republish 0.8.2 for now via a manual trigger.
• How could this even happen in the first place? Shouldn't this be checked by our tests?

[Scienfitz]

The doc has been republished from 0.8.2 enabled by #230