ce-release-finalize

Automating a Python package release workflow involves coordinating version bumps, changelog updates, builds, validation, tagging, and publishing to PyPI. This skill orchestrates the entire end-to-end release process for calibrated-explanations, including post-release verification.

When bumping a release version, you typically need to update version strings across multiple project files. This skill ensures consistency by updating pyproject.toml, __init__.py, CITATION.cff, docs/conf.py, and METADATA.json automatically during the release workflow.

To build, tag, and publish a Python package, you run build commands, validate artifacts, tag the release in version control, and publish to PyPI and Read the Docs. This skill automates these steps sequentially with built-in smoke tests and post-release verification.

Yes, release automation can update changelogs and documentation before publishing to PyPI. This skill coordinates changelog updates and documentation metadata changes as part of the pre-flight checks before building and publishing the release.

Release automation for calibrated-explanations is tailored to a specific project structure, updating defined files like pyproject.toml and CITATION.cff. It may not apply to projects with different file layouts, versioning schemes, or publishing targets outside of PyPI and Read the Docs.