Maxwell G

I also think `9` should be a standalone item in the version switcher.

This also applies to `hacking/tagger` that uses typer for CLI parsing

We discussed this in today's community meeting and folks seemed open to the idea. @mattclay, is this something you'd be willing to have in https://github.com/ansible/ansible/blob/devel/packaging/release.py or otherwise integrated into core's...

Yes, these tags are desired (at least by me they are :). The goal here is to simply record the state of this repository after each ansible-core release. For now,...

> For now, I guess I can push the tags manually https://github.com/ansible/ansible-documentation/releases/tag/v2.15.2 https://github.com/ansible/ansible-documentation/releases/tag/v2.14.8 https://github.com/ansible/ansible-documentation/releases/tag/v2.13.11

We need tagged releases in order to properly retrieve ansible-core porting guides in a reproducible fashion when creating the ansible combined porting guide. Currently, we retrieve the latest file from...

I'm talking about needing the tags for core porting guides. The combined porting guides that are created as part of the `ansible` package build process are indeed created after the...

- https://github.com/ansible/ansible-documentation/releases/tag/v2.14.9rc1 - https://github.com/ansible/ansible-documentation/releases/tag/v2.15.3rc1

By the way, https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/ansible/tag.py is the script I've been using to create these tags. It makes some assumptions about how I set up my git clones, so it may be...

- https://github.com/ansible/ansible-documentation/releases/tag/v2.13.12rc1 - https://github.com/ansible/ansible-documentation/releases/tag/v2.14.10rc1 - https://github.com/ansible/ansible-documentation/releases/tag/v2.15.4rc1