release-engineering

Version sync aligns numbers across package metadata, installers, constants, generated references, and tests to prevent mismatches. You coordinate these updates before finalizing the release commit to ensure consistent versioning across all project artifacts.

Release verification gating enforces typecheck, full tests, dependency audit, and release-specific verification before any release commit is treated as final. These CI checks act as mandatory gates to prevent broken releases caused by incomplete verification.

Changelog preparation summarizes user-facing changes, fixes, dependency/security changes, and verification evidence while noting residual risks and known limitations. This evidence-based approach ensures the changelog serves as a verifiable record of release readiness.

Disciplined release engineering requires pushing the release commit first, then creating the git tag. Following this exact commit/push/tag order prevents orphaned tags and ensures the release history remains consistent across all environments.

Version synchronization fails when package metadata, installers, constants, generated references, and tests are not aligned. Release debugging requires reviewing git status and diff to identify mismatches and applying a Plan-Execute-Review-Verify-Report workflow.