FWIW, native versioning support is on Zensical's long-term roadmap (see zensical/backlog#45).

In the mean-time, they've shipped a tailored and official fork of mike for Zensical.

Lastly, if all that's immediately desired is just separating released versus unreleased docs, zizmor can either:

1. Change the docs publish workflow to only occur as part of the release flow
2. Alternatively, if you wish to still have the unreleased docs be publicly accessible, publish exactly two versions --"stable/released" versus "unstable/dev").

Happy to take a stab at any of the above paths if you would like some help :)

(2) seems fine to me, although I'm concerned that users are still going to trip themselves up here -- I suspect a lot of people will visit the unstable docs thinking they're stable or vice versa.

I wonder if there's a way to add a "you are reading docs for an unreleased version" callout, similar to what SQLAlchemy and others do.

(Separately, there's a link breakage risk -- the current links have to keep working! But I think it would be fine if the current links remained for the stable version and we picked a path or whatever for the unstable docs.)

Thank you for being receptive to feedback!