bump-publish

Automating Python package versioning and publishing to PyPI involves incrementing versions in pyproject.toml and __init__.py, building the package, and uploading it. This skill automates that entire workflow, including git tagging, for patch, minor, or major releases.

Yes, you can test a PyPI release without uploading by using a dry-run mode. This allows you to verify version increments in pyproject.toml and the build process without committing changes, tagging git, or uploading the final package to the registry.

To bump a minor version across pyproject.toml and __init__.py, you can use an automated bumping tool. This skill specifically locates and updates the version strings in both files simultaneously, then commits the version increment and tags it in git.

Yes, automated version bumping handles git tagging and committing. When you increment the package version, the process automatically commits the updated pyproject.toml and __init__.py files and creates a corresponding git tag for the release.

The best way to release a patch update to PyPI is to use an automated release workflow. This ensures the patch version is correctly incremented across all configuration files, built properly, and uploaded safely without manual file editing errors.