Every time a release is requested, individual steps (commit, push, tag, GitHub Release, PyPI verification) are done partially and the user has to prompt for each subsequent step. The agent stops after one or two steps and reports success without completing the full pipeline.
What happens:
- Tag is created but no GitHub Release object
- Changelog is written but not pushed
- Local branch is left diverged from remote
- PyPI publish is never triggered or verified
- Agent reports "done" after partial completion
Why:
- No documented release checklist exists in the project
tag-release.yml creates and pushes tags but does NOT create a GitHub Release
pypi-publish.yml requires manual workflow_dispatch — not triggered by tags
- Agent interprets "release" narrowly (tag only) instead of end-to-end
Suggested fixes:
- Add a release procedure checklist to AGENTS.md or a knowledge file — the complete pipeline from commit through PyPI verification
- Add a step to
tag-release.yml that creates the GitHub Release via gh release create after pushing the tag
- Add a tag-push trigger to
pypi-publish.yml so publishing isn't a separate manual step
- The release procedure should be: commit → push → PR → merge → version bump → changelog → tag → GitHub Release → PyPI publish → verify both exist
Every time a release is requested, individual steps (commit, push, tag, GitHub Release, PyPI verification) are done partially and the user has to prompt for each subsequent step. The agent stops after one or two steps and reports success without completing the full pipeline.
What happens:
Why:
tag-release.ymlcreates and pushes tags but does NOT create a GitHub Releasepypi-publish.ymlrequires manualworkflow_dispatch— not triggered by tagsSuggested fixes:
tag-release.ymlthat creates the GitHub Release viagh release createafter pushing the tagpypi-publish.ymlso publishing isn't a separate manual step