What problem does it solve? Releasing the Altera framework means bumping versions across five interdependent packages (server, client, tools, skills, create), keeping a dozen version pins in sync, and publishing to JSR in the right order — a process where a forgotten bump or wrong pin silently ships broken packages, and JSR publication is irreversible. ## Core Features & Use Cases - Version pin discipline: Explains the single source of truth (<package>/deno.json → version) and every pin location across create/template/deno.json, create/deno.json, tools/deno.json, Dockerfile, and docker-compose.yml, enforced by scripts/version-pins_test.ts. - Coupled release rules: Defines which packages must move together (client→skills, client→vite, server→tools, server→SQL cores) and how to choose patch vs minor before 1.0. - Publication workflow: Covers CHANGELOG.md updates, pre-publish checks (deno task check:deps, test:unit, scaffold:verify:local, deno publish --dry-run), the push-triggered Publish to JSR workflow, post-release verification, and fix-release recovery. - Use Case: You changed the public API of @altera/server and need to release: the skill walks you through bumping server and tools, updating the changelog, running dry-run publishes, and verifying the post-release scaffold check. ## Quick Start Tell the assistant which Altera package changed and what changed in it, and ask it to prepare the release following the framework-release skill.
