Automate the spek release process — update CHANGELOGs, bump version, create tag, and push to trigger CI/CD.

Input: Optionally specify a version bump type (patch, minor, major) or an explicit version (e.g., 0.3.0). If omitted, ask.

Steps

1. Determine version bump

   If the user provided a bump type or version, use it. Otherwise, use AskUserQuestion to ask:

   Options: patch, minor, major

   Show the current version from root package.json and what each option would result in.

2. Gather changelog content

   Look at archived changes since the last release to identify what's new:

   • Check openspec/changes/archive/ for changes archived after the last release
   • Check recent git commits for context
   • Draft changelog bullet points summarizing user-facing changes

   Show the draft and ask the user to confirm or edit.

3. Update CHANGELOGs

   Update ALL THREE changelog files (they must stay in sync per project convention):

   • CHANGELOG.md (root)
   • packages/vscode/CHANGELOG.md
   • packages/intellij/CHANGELOG.md

   Add a new version section at the top with the changelog content.

4. Commit changelog updates

   bash
   1git add CHANGELOG.md packages/vscode/CHANGELOG.md packages/intellij/CHANGELOG.md
   2git commit -m "Update CHANGELOG for v<version>"

5. Rebuild demo page

   Rebuild docs/demo.html so it reflects the latest code and openspec content:

   bash
   1npm run build:demo

   Stage the updated demo file:

   bash
   1git add docs/demo.html
   2git commit -m "Rebuild demo for v<version>"

6. Run npm version

   bash
   1npm version <type-or-version> --no-git-tag-version

   Wait — the version lifecycle script in package.json auto-syncs to packages/vscode/package.json and packages/intellij/gradle.properties.

   Actually, use the standard flow which auto-commits and tags:

   bash
   1npm version <type-or-version>

   This will:

   • Bump root package.json version
   • Run version script (syncs packages/vscode/package.json + packages/intellij/gradle.properties + git add)
   • Create git commit with version
   • Create v<version> git tag

7. Push to trigger CI/CD

   Ask the user for confirmation before pushing:

   "Ready to push v<version> to origin? This will trigger the CI/CD pipelines to publish to VS Code Marketplace and JetBrains Marketplace."

   bash
   1git push --follow-tags

8. Show summary

   Display:

   • New version number
   • Changelog content
   • Git tag created
   • CI/CD status: "Pushed. GitHub Actions will publish to VS Code Marketplace and JetBrains Marketplace."
   • Remind: "Monitor the workflows at: https://github.com/<owner>/<repo>/actions"

Guardrails

• ALWAYS update all three CHANGELOGs (root + vscode + intellij) — they must be identical
• ALWAYS confirm with user before git push
• If there are uncommitted changes, warn and ask to stash or commit first
• If the working tree is dirty after changelog update, stage only changelog files
• Do NOT push without explicit user confirmation