ship

Git release automation handles version bumps, changelog updates, and tag creation end-to-end. It validates the dev branch, runs tests, and commits synced version metadata across files like pyproject.toml before pushing tags to main.

The dev to main release workflow merges feature branches by running tests, updating docs and changelogs, bumping pyproject.toml versions, amending metadata comments, and creating a clean git tag commit set on the main branch.

Yes, automated release management asserts test success and updates documentation before tagging. It provides guardrails by safely aborting the release process if tests fail or error checks detect metadata sync issues across files.

Yes, this release automation reads and updates docs/changelog.mdx, bumps the pyproject.toml version, and amends version comments in skill metadata files to ensure all version references are synced before creating the git tag.

If tests fail during the version bump workflow, the automation includes error checks that trigger a safe abort. This prevents incomplete commits, unsynced version metadata, or invalid git tags from being pushed to the main branch.

The best way to ensure consistent versioning is using an end-to-end release automation pattern. It standardizes the multi-step workflow of bumping versions, updating changelogs, syncing metadata, and creating git tags to eliminate manual release errors.