openskills-release-ops

Release readiness validation checks runtime compilation, binding builds, example sanity, and version consistency. This skill automates that verification process using cargo, providing a deterministic checklist and a clear go/no-go outcome based on the results.

A deterministic release gate checklist systematically verifies runtime status, binding builds, example sanity, and version consistency before publishing. It eliminates guesswork by enforcing strict prerequisite checks and returning a definitive go/no-go decision.

Yes, cargo is required for build and test verification. The release validation process depends on it to compile the runtime, execute tests, and verify packaging prerequisites before generating a go/no-go outcome.

Checking binding readiness involves verifying that Python and TypeScript bindings build correctly alongside the runtime. This skill automates these prerequisite checks to ensure version consistency and example sanity before release.

The best way to ensure packaging prerequisites are met is to run an automated release gate verification. This skill checks runtime status, binding builds, and changelog accuracy to provide a deterministic go/no-go outcome before pushing a new version.

Release validation can fail when the runtime compiles if other checklist items fail, such as Python or TypeScript binding builds, example sanity checks, or changelog updates. The release gate requires all packaging prerequisites to pass for a go decision.