Release checklist

Use this checklist before publishing packages or updating the starters. CI runs the same core gates, but doing them locally catches release drift before a PR waits on Actions.

Package gates

pnpm check

check is the authoritative package gate. It verifies synchronized package and standalone-starter manifest/lockfile versions, lint and formatting, builds, tests, packed package manifests, and both complete starter gates.

After publishing a new package version, update the standalone consumers and their lockfiles before changing starter code:

pnpm starter:sync <published-version>

This is deliberately post-publication: release PRs cannot install the package version they are preparing to publish.

Starter gates

Run each starter from its own directory because each is intentionally standalone:

cd starter/astro
pnpm install --frozen-lockfile
pnpm check

cd starter/tanstack
pnpm install --frozen-lockfile
pnpm check

The smoke checks assert the /blog and /blog/{slug} demo, contentbit metadata, keyword usage, generated backlinks, first-run script names, contentbit dependency versions, and starter build output. They are not a replacement for visual review, but they catch broken demo wiring quickly.

For visual review, run pnpm studio in the starter and open http://localhost:4377, then stop the server before continuing.

Content and docs

• Regenerate docs artifacts after docs changes with pnpm --filter @contentbit/site prebuild.
• Confirm internal-link docs cover the active locale strategy when changing resolver behavior.
• Keep starter article keywords present in the article body, not only in frontmatter.
• When changing Astro rendering behavior, confirm the prose path still belongs to Astro/Sätteri and contentbit remains the block validation/rendering layer.