What problem does it solve? Publishing the @astroblocks/astro-blocks package involves strict tag formats, a machine-parsed changelog contract, provenance attestation, and dist-tag rules; a single formatting mistake silently aborts the release workflow. ## Core Features & Use Cases - Tag and Version Validation: Enforces the vX.Y.Z or vX.Y.Z-alpha.N tag format and requires exact match with package.json version before publishing. - Changelog Contract: Defines the required ## [X.Y.Z] - YYYY-MM-DD header and mandatory ### Title sub-heading parsed by the extract-changelog-entry script. - Dist-Tag and Provenance Rules: Documents that stable releases get only the latest tag while pre-releases get both latest and alpha, and that npm publish --provenance is mandatory. - Use Case: Before cutting release 1.2.0, follow the pre-release checklist to commit a valid changelog entry, run npm version minor, push with --follow-tags, and confirm dist-tags with npm view. ## Quick Start Ask the assistant to walk you through cutting a new stable release of astro-blocks, including the changelog entry, version bump, tag push, and dist-tag verification.
