Add ansible-lint CI gate and antsibull-changelog release pipeline #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/ci-lint-and-release-gate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rolls out the pattern proven on silvarion.repos/base/containers/databases/network/provision. Created changelogs/config.yaml (didn't exist at all).
Fixed real issues: a redundant top-level requires_ansible key in galaxy.yml, 5 molecule files missing a trailing newline, and two stale changelog fragments (1.0.0.yml, 1.1.0.yml) left behind from past releases done by hand-editing changelog.yaml directly, bypassing antsibull-changelog -- both versions' content already exists correctly in changelog.yaml/CHANGELOG.rst, so these were pure duplicates blocking any future release with "Found prelude section 'release_summary' more than once!". Deleted both.
Verified antsibull-changelog release+generate end-to-end in a fresh container: fails with that exact error before deleting the stale fragments, succeeds after.
🤖 Generated with Claude Code
https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp
Rolls out the pattern proven on silvarion.repos/base/containers/ databases/network/provision. This collection had no changelogs/ config.yaml at all -- created one matching the fleet's standard shape. Fixed real issues: - galaxy.yml had a redundant top-level `requires_ansible` key (not part of the official schema, fatal under the basic profile); removed it. - 5 molecule/*/*.yml files were missing a trailing newline. - changelogs/fragments/1.0.0.yml and 1.1.0.yml were stale, already- consumed fragments left behind from past releases that were done by hand-editing changelogs/changelog.yaml directly, bypassing antsibull-changelog entirely (confirmed: both versions' full release_summary/major_changes/minor_changes content already exists correctly in changelog.yaml and CHANGELOG.rst, dated 2026-04-16 and 2026-05-11). Because the fragments were never actually consumed by the tool, keep_fragments: false never got a chance to clean them up -- antsibull-changelog release blocked entirely on both still declaring their own release_summary ("Found prelude section 'release_summary' more than once!"). Deleted both; their content is not lost, it's already baked into changelog.yaml/CHANGELOG.rst. Verified antsibull-changelog release+generate end-to-end in a fresh container matching the CI job image -- fails with the exact duplicate-prelude error above before deleting the stale fragments, succeeds after. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp