release

Automate Python package releases by coordinating semver versioning, database asset validation, and PyPI publishing. This ensures SQLite assets and code updates are synchronized safely across the registry-research-toolkit repository during deployment.

Managing version bumps involves automated semver versioning and changelog generation before publishing to PyPI. The release pipeline enforces pre-release testing and schema validation, requiring explicit confirmation for major version bumps to prevent broken deployments.

Yes, you need uv and gh installed along with zstd, pytest, and ruff. These dependencies execute environment management, GitHub release creation, asset compression, integration testing, and code linting throughout the end-to-end release lifecycle.

Schema versioning validation works by enforcing strict checks during the pre-release phase. It verifies that database asset schemas are correct and synchronized before allowing any package deployment to proceed to PyPI or GitHub releases.

Yes, you can use this process for major version bumps, but it requires explicit confirmation. Safety guardrails enforce pre-release testing and schema validation to ensure automated deployment verification passes before completing major version releases.

Release pipelines fail during database asset generation when schema version validation or integration testing encounters errors. The safety guardrails intentionally block deployment to prevent broken releases when SQLite assets are not properly synchronized.