Fix release workflow's real root cause: install ansible-core too #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/release-install-ansible-core"
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?
Found via a real container reproduction (node:20-bookworm, matching the CI job image), with
-vfor the actual traceback that CI's job log never surfaces:antsibull-changelog shells out to
ansible-docto detect the installed ansible-core version. Only antsibull-changelog itself was being pip-installed, so that binary never existed, and every run failed here regardless of what came before or after in the workflow.The previous three fixes (
743a71c,a8b68a6,aa07c70) were chasing a real but unrelated non-blocking-stdio bug that only ever existed in one of my own local interactive shell sessions -- confirmed by reproducing the actual CI failure in a fresh container from scratch, where that bug doesn't occur at all. This reverts that extra complexity and fixes the real cause:pip3 install ... antsibull-changelog ansible-core.Verified end-to-end in the same container: apt/pip install, sed version bump,
antsibull-changelog release+generate, and git commit+tag all succeed with ansible-core installed alongside antsibull-changelog.🤖 Generated with Claude Code
https://claude.ai/code/session_012icUrjv3vgHtovVpHUFjdp