Name: release
Author: dyher

Prompt file imported from dyher/lithos (.github/prompts/release.prompt.md). Copyright stays with the author.

You are performing a Neolith driver release. Follow every step in order. Stop and ask the user before any destructive or irreversible action (git push, tagging, GitHub release creation).

Context

Repository: h:\github\neolith
Version source: CMakeLists.txt, line starting with VERSION inside the project() block. The format is MAJOR.MINOR.PATCH.

Release notes: docs/ChangeLog.md. Format for a new section:

### X.Y.Z-<qualifier> — YYYY-MM-DD

#### Changes since X.Y.Z-<prev>
- <sha7> <type>: <description> (#<PR>)

Binary compatibility sentinel: lib/lpc/program/binaries.c, driver_id (hex date stamp). Bump only when opcodes or runtime struct sizes changed.

Step 1 — Verify working tree is clean

Run:

git -C h:\github\neolith status --short

If there are uncommitted changes, stop and tell the user. Do not proceed until the working tree is clean.

Step 2 — Determine current and new version

Read CMakeLists.txt and extract the current VERSION value.
Read docs/ChangeLog.md and identify the most recently released version (the first ### heading that has a date, not "unreleased").
Ask the user: "What should the new version be?" — show the current version and suggest a reasonable increment (patch bump by default). Also ask: "Is this a pre-release? If so, what qualifier? (e.g. alpha.8)"

Step 3 — Collect commits since last release

Run:

git -C h:\github\neolith log <last-tag>..HEAD --oneline --no-merges

Where <last-tag> is the git tag for the previously released version (e.g. v1.0.0-alpha.7). If the tag doesn't exist, use the SHA from the ChangeLog.

Group the commits by conventional-commit prefix:

feat: → Features
fix: → Bug Fixes
clean: / refactor: → Cleanup
chore: / ci: → Chores
doc: → Documentation
everything else → Other

Step 4 — Update docs/ChangeLog.md

Insert a new section immediately after the ## neolith-X.Y.Z (unreleased) heading (or replace that heading if this is the final release of that milestone). Use today's date (ISO 8601). Example:

### 1.0.0-alpha.8 — 2026-03-25

#### Changes since 1.0.0-alpha.7
- abc1234 feat: add cool feature (#300)
- def5678 fix: crash in interpreter (#299)

Show the user the proposed diff before writing.

Step 5 — Bump version in CMakeLists.txt

Replace the VERSION line in CMakeLists.txt with the new version (MAJOR.MINOR.PATCH only — no qualifier; qualifiers go in ChangeLog and git tags).

Step 6 — Check driver_id

Ask the user: "Were any opcodes added, removed, or reordered, or were any runtime structs resized since the last release?"

If yes: open lib/lpc/program/binaries.c and update driver_id to a new hex date stamp reflecting today (format 0xYYYYMMDD). Show them the proposed change.

Step 7 — Run tests

Run the CI preset tests and report results:

cmake --build --preset ci-linux
ctest --preset ut-linux

(On Windows without WSL, use ci-vs16-x64 / ut-vs16-x64 or ci-clang-x64 / ut-clang-x64.)

Do not proceed if tests fail. Summarize any failures for the user.

Step 8 — Commit release changes on a release branch and open a PR

The main branch is protected, so do not commit directly to main.

Show the user the list of files changed (ChangeLog.md, CMakeLists.txt, and optionally binaries.c). Ask for confirmation, then run:

git checkout -b release/v<NEW_VERSION>
git add docs/ChangeLog.md CMakeLists.txt lib/lpc/program/binaries.c
git commit -m "chore: release v<NEW_VERSION>"
git push -u origin release/v<NEW_VERSION>

Then create a PR from release/v<NEW_VERSION> into main, request review, and wait for it to be merged. Do not proceed to tagging until the PR is merged.

Step 9 — Create and push the tag after PR merge

After Step 8 PR is merged into main, ask the user to confirm before running:

git checkout main
git pull --ff-only origin main
git tag -a v<NEW_VERSION> -m "Release v<NEW_VERSION>"
git push origin v<NEW_VERSION>

Step 10 — Create GitHub release

Using the GitHub MCP tool, create a GitHub release for the tag v<NEW_VERSION> with:

Title: neolith v<NEW_VERSION>
Body: the ChangeLog section you wrote in Step 4 (markdown)
Pre-release: true if a qualifier (alpha/beta/rc) is present, false otherwise

Ask the user to confirm before creating.

Done

Summarize what was done: version bumped, ChangeLog updated, tag pushed, release created. Mention any steps that were skipped and why.

You are performing a Neolith driver release. Follow every step in order. Stop and ask the user before any destructive or irreversible action (git push, tagging, GitHub release creation). ## Context - Repository: `h:\github\neolith` - Version source: `CMakeLists.txt`, line starting with `VERSION` inside the `project()` block. The format is `MAJOR.MINOR.PATCH`. - Release notes: `docs/ChangeLog.md`. Format for a new section: ``` ### X.Y.Z-<qualifier> — YYYY-MM-DD #### Changes since X.Y.Z-<prev> - <sha7> <type>: <description> (#<PR>) ``` - Binary compatibility sentinel: `lib/lpc/program/binaries.c`, `driver_id` (hex date stamp). Bump only when opcodes or runtime struct sizes changed. ## Step 1 — Verify working tree is clean Run: ``` git -C h:\github\neolith status --short ``` If there are uncommitted changes, stop and tell the user. Do not proceed until the working tree is clean. ## Step 2 — Determine current and new version 1. Read `CMakeLists.txt` and extract the current `VERSION` value. 2. Read `docs/ChangeLog.md` and identify the most recently released version (the first `###` heading that has a date, not "unreleased"). 3. Ask the user: **"What should the new version be?"** — show the current version and suggest a reasonable increment (patch bump by default). Also ask: **"Is this a pre-release? If so, what qualifier? (e.g. alpha.8)"** ## Step 3 — Collect commits since last release Run: ``` git -C h:\github\neolith log <last-tag>..HEAD --oneline --no-merges ``` Where `<last-tag>` is the git tag for the previously released version (e.g. `v1.0.0-alpha.7`). If the tag doesn't exist, use the SHA from the ChangeLog. Group the commits by conventional-commit prefix: - `feat:` → Features - `fix:` → Bug Fixes - `clean:` / `refactor:` → Cleanup - `chore:` / `ci:` → Chores - `doc:` → Documentation - everything else → Other ## Step 4 — Update docs/ChangeLog.md Insert a new section immediately after the `## neolith-X.Y.Z (unreleased)` heading (or replace that heading if this is the final release of that milestone). Use today's date (ISO 8601). Example: ```markdown ### 1.0.0-alpha.8 — 2026-03-25 #### Changes since 1.0.0-alpha.7 - abc1234 feat: add cool feature (#300) - def5678 fix: crash in interpreter (#299) ``` Show the user the proposed diff before writing. ## Step 5 — Bump version in CMakeLists.txt Replace the `VERSION` line in `CMakeLists.txt` with the new version (MAJOR.MINOR.PATCH only — no qualifier; qualifiers go in ChangeLog and git tags). ## Step 6 — Check driver_id Ask the user: **"Were any opcodes added, removed, or reordered, or were any runtime structs resized since the last release?"** If yes: open `lib/lpc/program/binaries.c` and update `driver_id` to a new hex date stamp reflecting today (format `0xYYYYMMDD`). Show them the proposed change. ## Step 7 — Run tests Run the CI preset tests and report results: ``` cmake --build --preset ci-linux ctest --preset ut-linux ``` (On Windows without WSL, use `ci-vs16-x64` / `ut-vs16-x64` or `ci-clang-x64` / `ut-clang-x64`.) Do not proceed if tests fail. Summarize any failures for the user. ## Step 8 — Commit release changes on a release branch and open a PR The `main` branch is protected, so do not commit directly to `main`. Show the user the list of files changed (ChangeLog.md, CMakeLists.txt, and optionally binaries.c). Ask for confirmation, then run: ``` git checkout -b release/v<NEW_VERSION> git add docs/ChangeLog.md CMakeLists.txt lib/lpc/program/binaries.c git commit -m "chore: release v<NEW_VERSION>" git push -u origin release/v<NEW_VERSION> ``` Then create a PR from `release/v<NEW_VERSION>` into `main`, request review, and wait for it to be merged. Do not proceed to tagging until the PR is merged. ## Step 9 — Create and push the tag after PR merge After Step 8 PR is merged into `main`, ask the user to confirm before running: ``` git checkout main git pull --ff-only origin main git tag -a v<NEW_VERSION> -m "Release v<NEW_VERSION>" git push origin v<NEW_VERSION> ``` ## Step 10 — Create GitHub release Using the GitHub MCP tool, create a GitHub release for the tag `v<NEW_VERSION>` with: - **Title**: `neolith v<NEW_VERSION>` - **Body**: the ChangeLog section you wrote in Step 4 (markdown) - **Pre-release**: true if a qualifier (alpha/beta/rc) is present, false otherwise Ask the user to confirm before creating. ## Done Summarize what was done: version bumped, ChangeLog updated, tag pushed, release created. Mention any steps that were skipped and why.

{ "prompt": "You are performing a Neolith driver release. Follow every step in order. Stop\nand ask the user before any destructive or irreversible action (git push,\ntagging, GitHub release creation).\n\n## Context\n\n- Repository: `h:\\github\\neolith`\n- Version source: `CMakeLists.txt`, line starting with `VERSION` inside the\n `project()` block. The format is `MAJOR.MINOR.PATCH`.\n- Release notes: `docs/ChangeLog.md`. Format for a new section:\n ```\n ### X.Y.Z-<qualifier> — YYYY-MM-DD\n\n #### Changes since X.Y.Z-<prev>\n - <sha7> <type>: <description> (#<PR>)\n ```\n- Binary compatibility sentinel: `lib/lpc/program/binaries.c`, `driver_id`\n (hex date stamp). Bump only when opcodes or runtime struct sizes changed.\n\n## Step 1 — Verify working tree is clean\n\nRun:\n```\ngit -C h:\\github\\neolith status --short\n```\n\nIf there are uncommitted changes, stop and tell the user. Do not proceed until\nthe working tree is clean.\n\n## Step 2 — Determine current and new version\n\n1. Read `CMakeLists.txt` and extract the current `VERSION` value.\n2. Read `docs/ChangeLog.md` and identify the most recently released version\n (the first `###` heading that has a date, not \"unreleased\").\n3. Ask the user: **\"What should the new version be?\"** — show the current\n version and suggest a reasonable increment (patch bump by default).\n Also ask: **\"Is this a pre-release? If so, what qualifier? (e.g. alpha.8)\"**\n\n## Step 3 — Collect commits since last release\n\nRun:\n```\ngit -C h:\\github\\neolith log <last-tag>..HEAD --oneline --no-merges\n```\n\nWhere `<last-tag>` is the git tag for the previously released version (e.g.\n`v1.0.0-alpha.7`). If the tag doesn't exist, use the SHA from the ChangeLog.\n\nGroup the commits by conventional-commit prefix:\n- `feat:` → Features\n- `fix:` → Bug Fixes\n- `clean:` / `refactor:` → Cleanup\n- `chore:` / `ci:` → Chores\n- `doc:` → Documentation\n- everything else → Other\n\n## Step 4 — Update docs/ChangeLog.md\n\nInsert a new section immediately after the `## neolith-X.Y.Z (unreleased)`\nheading (or replace that heading if this is the final release of that\nmilestone). Use today's date (ISO 8601). Example:\n\n```markdown\n### 1.0.0-alpha.8 — 2026-03-25\n\n#### Changes since 1.0.0-alpha.7\n- abc1234 feat: add cool feature (#300)\n- def5678 fix: crash in interpreter (#299)\n```\n\nShow the user the proposed diff before writing.\n\n## Step 5 — Bump version in CMakeLists.txt\n\nReplace the `VERSION` line in `CMakeLists.txt` with the new version\n(MAJOR.MINOR.PATCH only — no qualifier; qualifiers go in ChangeLog and git\ntags).\n\n## Step 6 — Check driver_id\n\nAsk the user: **\"Were any opcodes added, removed, or reordered, or were any\nruntime structs resized since the last release?\"**\n\nIf yes: open `lib/lpc/program/binaries.c` and update `driver_id` to a new hex\ndate stamp reflecting today (format `0xYYYYMMDD`). Show them the proposed\nchange.\n\n## Step 7 — Run tests\n\nRun the CI preset tests and report results:\n```\ncmake --build --preset ci-linux\nctest --preset ut-linux\n```\n(On Windows without WSL, use `ci-vs16-x64` / `ut-vs16-x64` or\n`ci-clang-x64` / `ut-clang-x64`.)\n\nDo not proceed if tests fail. Summarize any failures for the user.\n\n## Step 8 — Commit release changes on a release branch and open a PR\n\nThe `main` branch is protected, so do not commit directly to `main`.\n\nShow the user the list of files changed (ChangeLog.md, CMakeLists.txt, and\noptionally binaries.c). Ask for confirmation, then run:\n\n```\ngit checkout -b release/v<NEW_VERSION>\ngit add docs/ChangeLog.md CMakeLists.txt lib/lpc/program/binaries.c\ngit commit -m \"chore: release v<NEW_VERSION>\"\ngit push -u origin release/v<NEW_VERSION>\n```\n\nThen create a PR from `release/v<NEW_VERSION>` into `main`, request review,\nand wait for it to be merged. Do not proceed to tagging until the PR is merged.\n\n## Step 9 — Create and push the tag after PR merge\n\nAfter Step 8 PR is merged into `main`, ask the user to confirm before running:\n\n```\ngit checkout main\ngit pull --ff-only origin main\ngit tag -a v<NEW_VERSION> -m \"Release v<NEW_VERSION>\"\ngit push origin v<NEW_VERSION>\n```\n\n## Step 10 — Create GitHub release\n\nUsing the GitHub MCP tool, create a GitHub release for the tag `v<NEW_VERSION>`\nwith:\n- **Title**: `neolith v<NEW_VERSION>`\n- **Body**: the ChangeLog section you wrote in Step 4 (markdown)\n- **Pre-release**: true if a qualifier (alpha/beta/rc) is present, false otherwise\n\nAsk the user to confirm before creating.\n\n## Done\n\nSummarize what was done: version bumped, ChangeLog updated, tag pushed, release\ncreated. Mention any steps that were skipped and why.", "variables": [], "notes": "Automate the Neolith release process: validate state, gather commits, update ChangeLog.md, bump CMakeLists.txt version, tag the release, and create a GitHub release with generated notes. Tools: vscode, execute, read, agent, edit, search, web, browser, github/*, ms-vscode.cpp-devtools/Build_CMakeTools, ms-vscode.cpp-devtools/RunCtest_CMakeTools, ms-vscode.cpp-devtools/ListBuildTargets_CMakeTools.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/dyher/lithos", "path": ".github/prompts/release.prompt.md", "ref": "e3823d44a916714c636ae352fa6eaed8ebb6a770", "url": "https://github.com/dyher/lithos/blob/e3823d44a916714c636ae352fa6eaed8ebb6a770/.github/prompts/release.prompt.md", "key": "dyher/lithos/.github/prompts/release.prompt.md" } } }

release

About