release-schema

Automating semantic versioning and PyPI releases requires bumping local version files, generating documentation, and triggering a GitHub Actions workflow to publish the package. This process handles patch, minor, and major version bumps automatically.

Before automating a PyPI package release, you need local version files, a CHANGELOG, RATIONALE, and FIELD-MAPPINGS documents, plus a configured GitHub Actions workflow for PyPI publishing to execute the deployment.

Semantic versioning bumps the package version number based on the change type: patch for fixes, minor for backward-compatible features, and major for breaking changes, ensuring the PyPI release reflects the correct update scope.

Yes, you can release a schema package to PyPI independently of the CLI and site components. The release automation process isolates the schema version bump, documentation generation, and publishing steps.

Automated PyPI release workflows require specific documentation files like CHANGELOG, RATIONALE, and FIELD-MAPPINGS to ensure that the published package includes updated, version-aligned documentation for users.

The best way to handle version bumping and changelog updates is to automate the process using a script that applies semantic versioning rules and regenerates documentation alongside the version bump before publishing.