We should consider recording which antsibull version was used to build an antsibull release/generate its data for reproducibility purposes. Currently, it's recorded in the build-ansible.sh script in the sdist, but this is not the most accessible. I would have the ansible-community command that we added a few releases ago (maybe more than a few at this point?), print out the antsibull version, and also include it in the ansible-build-data repo. I would just create a new ansible-{version}-build-info.yaml file. It's not really a good fit for the .deps file, I don't think, and there's a lot of codepaths that would need to be fixed to not treat the key as a collection (adding the _python key broke a few things).
We should consider recording which antsibull version was used to build an antsibull release/generate its data for reproducibility purposes. Currently, it's recorded in the
build-ansible.shscript in the sdist, but this is not the most accessible. I would have theansible-communitycommand that we added a few releases ago (maybe more than a few at this point?), print out the antsibull version, and also include it in the ansible-build-data repo. I would just create a newansible-{version}-build-info.yamlfile. It's not really a good fit for the.depsfile, I don't think, and there's a lot of codepaths that would need to be fixed to not treat the key as a collection (adding the_pythonkey broke a few things).