release-checklist

Software release readiness is validated by checking versioning accuracy, changelog completeness, test execution, build artifacts, and rollback notes. This gatekeeping process prevents shipping unverified changes by enforcing deterministic checks across metadata and reproducible artifacts.

A release checklist for hotfix verification should include version validation across files, accurate changelog documentation, passing test execution, consistent build artifacts, and a captured rollback strategy. These checks ensure deterministic gates for releases and prevent incomplete code deployment.

Changelog accuracy and version matching are verified by confirming the version number in package files matches the changelog entry. This ensures user-visible changes are accurately documented and consistent metadata requirements are satisfied before tagging.

Automated release gates can check build artifacts and test execution. This Skill runs required tests and verifies build artifacts for consistency, ensuring deterministic gates for releases and reproducible build artifacts before shipment.

Rollback notes must be captured when preparing release candidates, cutting new versions, or verifying hotfixes. This ensures a strategy for rolling back changes is documented if necessary, preventing the shipment of unverified or incomplete code.

This release validation process works without external dependencies. It independently validates versioning, changelog accuracy, test execution, build artifacts, and rollback notes to ensure release readiness as a standalone gatekeeping mechanism.