Docs releases are tied to hatch version, not hatchling

[johanjk]

Was reading the docs looking for the new hatchling v1.22 dependencies for build hooks.

Surprised to not find it in the released docs, (but it is in dev docs). Maybe docs versions should track both hatch and hatchling versions.

[ofek]

I simply don't know how to do that since there is a single source of documentation. Do you have any ideas?

[johanjk]

The gh-pages source of truth already tracks the hatching v1.22 features under hatch 1.9 docs. Same goes for the latest gh-action artifact site.zip. Leading me to think that peaceiris/actions-gh-page somehow isn't seeing the changes. Would setting allow_empty_commit to true, publish the already present changes?

I think there is two paths forwards:

1. Make the docs version track both hatch and hatchling, eg. 1.9-1.22 would be the current doc version. by slightly changing set_release_version.py
2. Continue to hide hatchling version from the docs, but let it trigger pushes to gh-pages as described above.