How ansible-community/ansible-build-data works
ansible-build-data is a persistent release-data repository for the Ansible community package, not an application runtime. Release engineers coordinate release plans and collection changes, maintain per-major inputs and compatibility ranges, and use antsibull-build to produce version-specific dependency records. Other projects and scripts can refer to these records. The graph reflects the README and file tree; no runtime implementation was sampled, so edges describe documented stewardship and data use rather than internal calls.
Main entry points: ansible-11.build Compatibility ranges · ansible-11.13.0.deps Exact dependencies · ansible.in Collection list · ansible-11.13.0.yaml Release record
Components 15
Release planning
- GitHub issues
- Release milestones
- Community topics
Release inputs
- Collection list
11/ansible.in - Compatibility ranges
11/ansible-11.build
Release records
- Exact dependencies
11/ansible-11.13.0.deps - Release record
11/ansible-11.13.0.yaml - Release tags
11/ansible-11.13.0-tags.yaml - Release changelog
11/CHANGELOG-v11.md - Porting guide
11/porting_guide_11.rst
Collection information
- Collection metadata
11/collection-meta.yaml - Galaxy requirements
11/galaxy-requirements.yaml
Other components
- Release engineer
- antsibull-build
- Other projects and scripts
Connections 14
- Release engineer → GitHub issues: tracks issues
- Release engineer → Release milestones: checks releases
- Release engineer → Community topics: raises blockers
- Release engineer → Collection list: maintains list
- Release engineer → Compatibility ranges: sets ranges
- Release engineer → Collection metadata: maintains metadata
- Release engineer → Galaxy requirements: maintains requirements
- antsibull-build → Compatibility ranges: reads ranges
- antsibull-build → Exact dependencies: generates records
- Other projects and scripts → Exact dependencies: refers to versions
- Other projects and scripts → Release record: refers to releases
- Release engineer → Release changelog: tracks changes
- Release engineer → Porting guide: documents upgrades
- Release engineer → Release tags: maintains tags