Releases

Tag releases so fleets upgrade deliberately, document how to pin, and publish to Ansible Galaxy.

Items

• Tag semantic releases (galaxy.yml carries a version but nothing is tagged) and make examples/ pin this collection to a release instead of version: main, so fleets upgrade deliberately via dotpro requirements --upgrade — without pinning, one bad upstream merge reaches every machine within a day
• Document the pinning gradient: pin what you don't control, track what you do — dotfilespro.roles (upstream) pinned to a tag, an organizational company.roles collection on main because the org's own MR review is the gate and merging is the rollout, and the personal repo is by definition unpinned
• Publish the collection to Ansible Galaxy on each tagged release (CI job; register the dotfilespro namespace), so ansible-galaxy collection install dotfilespro.roles works without a git source and versions resolve via Galaxy's semver; organizational collections can publish under their own namespace the same way, or stay on git
• Add a badge row to the README: Galaxy collection version, pipeline status, license, GitLab stars