Coordinate version bumps, changelog updates, quality checks, and tagging for agr releases.
npx skills add https://github.com/computerlovetech/agr --skill agr-release
Please help me install this Agent Skill. Skill: agr-release Source: https://github.com/computerlovetech/agr/tree/main/skills/agr-release Command: npx skills add https://github.com/computerlovetech/agr --skill agr-release
It removes uncertainty and missed steps when cutting a new agr release, ensuring the version bump, changelog, quality checks, tagging, and publish pipeline all align so CI and PyPI publishing succeed.
Ask the AI to guide you through creating the next agr release by specifying whether you want a patch, minor, major, or beta release.
High-intent search queries and answers about installing and using this skill.
Automating Python package publishing with git tagging and GitHub Actions requires a tag-driven CI pipeline where a correct vX.Y.Z tag triggers the build and trusted PyPI publication. This workflow coordinates version bumping, changelog updates, and quality checks before pushing the tag to ensure the automated release succeeds.
Before cutting a PyPI release, you need a clean main-branch state, consistent changelog formatting, and locally passing ruff, pytest, and ty checks. Reconciling changes since the last release tag with the changelog ensures the generated GitHub Release notes are accurate.
To bump the version and update the changelog for a new release, identify what changed since the last tag, update the pyproject versioning, and format CHANGELOG.md consistently. Specifying a patch, minor, major, or beta release scopes the version bump appropriately.
A GitHub Actions publish workflow often fails after creating a git tag if local pre-release quality gates were skipped. Running the same linting, formatting, tests, and type checks locally before pushing the commit and tag prevents avoidable CI pipeline failures.
Triggering trusted PyPI publication through a CI pipeline requires a clean main-branch state. Committing and pushing a release tag with uncommitted changes or failing local checks misaligns the version bump and quality gates, causing the publish workflow to fail.
The best way to monitor a tag-driven GitHub Release and PyPI publishing pipeline is to guide the monitoring and verification of the publish workflow after pushing the confirmed commit and tag. This ensures the CI build succeeds and extracts the correct GitHub Release notes.
rohanbhatia27Configure Python projects with uv, ruff, ty, and pytest.
peeka-projectAutomate versioning, commit, tag, and push for GitHub releases.
Axel051171Automate version bumping, CHANGELOG updates, pre-release checks, and git tagging for UnifiedFloppyTool releases.
aliciaplsCoordinate Git workflows and PyPI publishing for Python SDK releases.
