The ansible-core project is still releasing 2.16 versions for downstream purposes even though 2.16 is EOL upstream. I removed 2.16 from the tagger script in the ansible/ansible-documentation repo back in November when 2.17 reached EOL. However since then core have released v2.16.15 and v2.16.16.
It probably makes sense to keep the tags in the ansible-documentation repo in sync, even though 2.16 is EOL upstream. I’ve created a PR to add that version back to the tagger script. If you have any thoughts on this, please reply either here or in the PR comments.
Another question might be re-publishing the 2.16 docs. It should be possible to build the docs by manually triggering the workflow even though all the build requirements haven’t been updated recently. I’m not sure if it’s worth going back and enabling workflows to bump dependencies for 2.16 and so on. We should be able to just build 2.16 docs as needed.
Keeping the tags make sense. I approved the PR for that. As for rebuilding the docs manually, I think that makes sense as long as the Core team agrees and we only build the core version of the docs (i.e., the version without community package docs and collection indices from Ansible 9 which is definitely EOL).
I’m wondering why we shouldn’t do a re-build of the Ansible 9 docs. After all, Ansible 9 depends on ansible-core >= 2.16, < 2.17, so when installing Ansible 9 now you get the new feature as well. And at some point we might have to rebuild the Ansible 9 docsite anyway for technical reasons, and instead of only adding the new feature at a random point in the future (when we do a rebuild for other reasons) I think it would be better to do a rebuild now so that users of the EOL Ansible 9 can at least look at the documentation of all features of it.
Or do we want to modify the documentation build process to stick to the latest released ansible-core version that didn’t have the feature? That could be more tricky since the docs build process for the ansible-core and the ansible docs right now doesn’t allow that distinction.