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

Release (MooshieUI)

Name: release
Author: Mooshieblob1

Full release path: repo hygiene → pre-commit → version bump → changelog → build validation → PR → GlassWorm → bot triage (all relevant PRs) → merge → tag → CI.

Inputs

Field	Default if omitted
Version `X.Y.Z`	Read `package.json`, patch+1 (no `v` prefix in files)
Summary	`git log` since last `v*` tag

Windows git (required)

git -c core.hooksPath=/dev/null ...

Pre-commit hook hangs in PowerShell without this.

Workflow

1. Repo hygiene — branches and open PRs [BLOCKING before new release branch]

Refresh remotes, inventory branches/PRs, and resolve conflicts before creating release/vX.Y.Z.

git fetch --prune origin
git branch -vv
git branch -r
gh pr list --state open --base main --json number,title,headRefName,updatedAt,isDraft
gh api repos/Mooshieblob1/MooshieUI/branches?per_page=100 --jq '.[].name'

Release / stale branch handling

Situation	Action
Remote `release/vX.Y.Z` already exists for this release	If PR is merged or abandoned: delete remote branch. If PR is still open and current: check out and continue on it (do not create a duplicate).
Remote `release/v` for an older* version, PR merged	Delete remote branch: `git -c core.hooksPath=/dev/null push origin --delete release/vOLD`
Remote `release/v` with closed* PR and no further work	Delete remote branch
Local tracking branches for deleted remotes	`git fetch --prune` then delete stale locals
Open PR targeting `main` that is superseded by this release	Close with a short comment, or merge first if it must ship in this release
Open PR with failing GlassWorm or blocking CI	Fix on that branch/PR or close before cutting the release

Do not force-push main or protected tags. Do not delete branches that still have unmerged work the user intends to ship.

Report a short table: branch/PR, status, action taken.

2. Bot review sweep — open PRs and recent merges

Before version bump, triage bot feedback on PRs that could block or duplicate this release.

Bots to read (non-exhaustive): gemini-code-assist[bot], copilot-pull-request-reviewer[bot], github-actions[bot] (only when comment contains a concrete fix).

# Open PRs targeting main
gh pr list --state open --base main --json number,title,headRefName

# Per PR (replace N):
gh pr view N --json reviews,comments,state,mergedAt
gh api repos/Mooshieblob1/MooshieUI/pulls/N/comments
gh api repos/Mooshieblob1/MooshieUI/pulls/N/reviews

Also check recently merged PRs since the last v* tag (bots sometimes comment late or on squash-merge commits):

$lastTag = git describe --tags --abbrev=0
gh pr list --state merged --base main --limit 20 --json number,title,mergedAt

Classify every bot comment using docs/BOT_REVIEW_TRIAGE.md:

Verdict	Action
Fix	Correctness, safety, MIME mismatches, consistency — fix on that PR's branch if still open, or on `main`/release branch if merged and release-blocking
Skip	Premature abstraction, nits, factually wrong bot claims — note rationale in release PR body or user summary
Defer	Valid but not release-blocking — document for follow-up; do not block tag

Release-blocking bot findings on open PRs must be resolved (fix or explicit skip with verification) before creating the release PR. If a fix belongs on another open PR, land it there first or cherry-pick into the release branch.

3. Pre-commit-check

Run pre-commit-check on current tree. Fix blockers; re-run until ✅.

4. Version bump (all three must match)

File	Field
`package.json`	`"version": "X.Y.Z"`
`src-tauri/Cargo.toml`	`version = "X.Y.Z"` under `[package]`
`src-tauri/tauri.conf.json`	`"version": "X.Y.Z"`

Verify:

Select-String -Pattern '"X.Y.Z"|version = "X.Y.Z"' package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json

5. Changelog files

Prepend to both RELEASE_NOTES.md and CHANGELOG.md:

## What's New in vX.Y.Z

### Group title
- Detail

---

## What's New in vPREVIOUS

CHANGELOG.md: new section goes directly under # Changelog.

6. Build validation [BLOCKING]

cargo check --manifest-path src-tauri/Cargo.toml
cargo check --manifest-path src-tauri/Cargo.toml --no-default-features --features server
cargo test --manifest-path src-tauri/Cargo.toml
npm run build

7. Release branch and PR

Confirm step 1: no conflicting release/vX.Y.Z on remote (unless intentionally continuing that PR).

git checkout main
git pull origin main
git checkout -b release/vX.Y.Z
git add -A
git -c core.hooksPath=/dev/null commit -m "vX.Y.Z: Short summary"
git -c core.hooksPath=/dev/null push -u origin release/vX.Y.Z
gh pr create --base main --head release/vX.Y.Z --title "vX.Y.Z: Short summary" --body "<bullet list of changes; note any bot triage from steps 1-2>"

8. CI

gh pr checks <PR_NUMBER> --watch --interval 30

Wait for GlassWorm Infection Audit SUCCESS (5 min timeout).

9. Bot review triage — release PR (and late comments)

Wait ~60s after CI green. Re-fetch all bot threads on the release PR:

gh pr view <PR_NUMBER> --json reviews,comments,state
gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments
gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/reviews

Repeat classification (Fix / Skip / Defer). Present a summary table: bot, file, verdict, one-line rationale.

Apply fixes only for Fix; then:

git add -A
git -c core.hooksPath=/dev/null commit -m "address bot review feedback"
git -c core.hooksPath=/dev/null push
gh pr checks <PR_NUMBER> --watch --interval 30

If bots post after a green run (common on squash-merge), re-poll comments once more before merge. Do not merge with unaddressed Fix items on the release PR.

10. Merge and sync main

gh pr merge <PR_NUMBER> --squash --delete-branch
git checkout main
git fetch origin main
git reset --hard origin/main

11. Post-merge bot pass (before tag)

On the merged release PR, fetch comments again in case bots reviewed the squash commit:

gh pr view <PR_NUMBER> --json comments,reviews,mergedAt
gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments

Fix on main: commit directly on main only if policy allows; otherwise open a tiny follow-up PR. For release workflow, prefer a fast follow-up commit on main before tagging when the fix is trivial and release-blocking.
If a Fix requires re-tagging content, complete the fix, then tag (never move/delete an existing tag).

12. Tag (after merge only)

Tags are protected — no force/delete. Tag must point at merged main:

git tag vX.Y.Z
git -c core.hooksPath=/dev/null push origin vX.Y.Z

v* tag triggers Build & Release (.github/workflows/release.yml).

13. Verify CI

gh run list --workflow=release.yml --limit 3

Tell user: https://github.com/Mooshieblob1/MooshieUI/actions

14. Fallback

If tag push fails or workflow does not start:

gh workflow run release.yml -f tag=vX.Y.Z

15. Cleanup

git fetch --prune origin
git -c core.hooksPath=/dev/null push origin --delete release/vX.Y.Z

Confirm no duplicate release/v* branches remain for this version. Prune stale local branches.

About UI

No manual About edit — version from __APP_VERSION__; release notes from GitHub Releases API at runtime.

Checklist

- [ ] Stale/existing branches and open PRs reviewed; release/* cleaned up or continued intentionally
- [ ] Bot comments triaged on open PRs + recent merges (Fix/Skip/Defer documented)
- [ ] Pre-commit-check passed
- [ ] Three version files match X.Y.Z
- [ ] RELEASE_NOTES.md + CHANGELOG.md updated
- [ ] cargo check + npm run build passed
- [ ] Release PR merged to main
- [ ] Post-merge bot pass completed (no unaddressed Fix items)
- [ ] Tag vX.Y.Z pushed
- [ ] Release workflow running
- [ ] Remote release/vX.Y.Z branch deleted

Mistakes to avoid

Missing one of the three version files
Skipping cargo check (stale Cargo.lock breaks CI)
Tag before PR merge
git without core.hooksPath=/dev/null on Windows
Force-updating tags — use workflow_dispatch instead
Creating a second release/vX.Y.Z while an open PR already exists for the same version
Merging the release PR while another open PR has release-blocking bot Fix items still unresolved
Ignoring late bot comments posted after CI goes green
Adding Co-Authored-By trailers to commits, PR bodies, or comments — never attribute AI assistance in any git or GitHub output

# Release (MooshieUI) Full release path: **repo hygiene → pre-commit → version bump → changelog → build validation → PR → GlassWorm → bot triage (all relevant PRs) → merge → tag → CI**. ## Inputs | Field | Default if omitted | |-------|-------------------| | Version `X.Y.Z` | Read `package.json`, patch+1 (no `v` prefix in files) | | Summary | `git log` since last `v*` tag | ## Windows git (required) ```text git -c core.hooksPath=/dev/null ... ``` Pre-commit hook hangs in PowerShell without this. ## Workflow ### 1. Repo hygiene — branches and open PRs [BLOCKING before new release branch] Refresh remotes, inventory branches/PRs, and resolve conflicts **before** creating `release/vX.Y.Z`. ```powershell git fetch --prune origin git branch -vv git branch -r gh pr list --state open --base main --json number,title,headRefName,updatedAt,isDraft gh api repos/Mooshieblob1/MooshieUI/branches?per_page=100 --jq '.[].name' ``` **Release / stale branch handling** | Situation | Action | |-----------|--------| | Remote `release/vX.Y.Z` already exists for **this** release | If PR is merged or abandoned: delete remote branch. If PR is still open and current: check out and continue on it (do not create a duplicate). | | Remote `release/v*` for an **older** version, PR merged | Delete remote branch: `git -c core.hooksPath=/dev/null push origin --delete release/vOLD` | | Remote `release/v*` with **closed** PR and no further work | Delete remote branch | | Local tracking branches for deleted remotes | `git fetch --prune` then delete stale locals | | Open PR targeting `main` that is superseded by this release | Close with a short comment, or merge first if it must ship in this release | | Open PR with failing **GlassWorm** or blocking CI | Fix on that branch/PR or close before cutting the release | **Do not** force-push `main` or protected tags. Do not delete branches that still have unmerged work the user intends to ship. Report a short table: branch/PR, status, action taken. ### 2. Bot review sweep — open PRs and recent merges Before version bump, triage bot feedback on PRs that could block or duplicate this release. **Bots to read** (non-exhaustive): `gemini-code-assist[bot]`, `copilot-pull-request-reviewer[bot]`, `github-actions[bot]` (only when comment contains a concrete fix). ```powershell # Open PRs targeting main gh pr list --state open --base main --json number,title,headRefName # Per PR (replace N): gh pr view N --json reviews,comments,state,mergedAt gh api repos/Mooshieblob1/MooshieUI/pulls/N/comments gh api repos/Mooshieblob1/MooshieUI/pulls/N/reviews ``` Also check **recently merged** PRs since the last `v*` tag (bots sometimes comment late or on squash-merge commits): ```powershell $lastTag = git describe --tags --abbrev=0 gh pr list --state merged --base main --limit 20 --json number,title,mergedAt ``` Classify every bot comment using [docs/BOT_REVIEW_TRIAGE.md](../../../docs/BOT_REVIEW_TRIAGE.md): | Verdict | Action | |---------|--------| | **Fix** | Correctness, safety, MIME mismatches, consistency — fix on that PR's branch if still open, or on `main`/release branch if merged and release-blocking | | **Skip** | Premature abstraction, nits, factually wrong bot claims — note rationale in release PR body or user summary | | **Defer** | Valid but not release-blocking — document for follow-up; do not block tag | **Release-blocking** bot findings on open PRs must be resolved (fix or explicit skip with verification) before creating the release PR. If a fix belongs on another open PR, land it there first or cherry-pick into the release branch. ### 3. Pre-commit-check Run **pre-commit-check** on current tree. Fix blockers; re-run until ✅. ### 4. Version bump (all three must match) | File | Field | |------|-------| | `package.json` | `"version": "X.Y.Z"` | | `src-tauri/Cargo.toml` | `version = "X.Y.Z"` under `[package]` | | `src-tauri/tauri.conf.json` | `"version": "X.Y.Z"` | Verify: ```powershell Select-String -Pattern '"X.Y.Z"|version = "X.Y.Z"' package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json ``` ### 5. Changelog files Prepend to **both** `RELEASE_NOTES.md` and `CHANGELOG.md`: ```markdown ## What's New in vX.Y.Z ### Group title - Detail --- ## What's New in vPREVIOUS ``` `CHANGELOG.md`: new section goes directly under `# Changelog`. ### 6. Build validation [BLOCKING] ```powershell cargo check --manifest-path src-tauri/Cargo.toml cargo check --manifest-path src-tauri/Cargo.toml --no-default-features --features server cargo test --manifest-path src-tauri/Cargo.toml npm run build ``` ### 7. Release branch and PR Confirm step 1: no conflicting `release/vX.Y.Z` on remote (unless intentionally continuing that PR). ```powershell git checkout main git pull origin main git checkout -b release/vX.Y.Z git add -A git -c core.hooksPath=/dev/null commit -m "vX.Y.Z: Short summary" git -c core.hooksPath=/dev/null push -u origin release/vX.Y.Z gh pr create --base main --head release/vX.Y.Z --title "vX.Y.Z: Short summary" --body "<bullet list of changes; note any bot triage from steps 1-2>" ``` ### 8. CI ```powershell gh pr checks <PR_NUMBER> --watch --interval 30 ``` Wait for **GlassWorm Infection Audit** SUCCESS (5 min timeout). ### 9. Bot review triage — release PR (and late comments) Wait ~60s after CI green. Re-fetch **all** bot threads on the release PR: ```powershell gh pr view <PR_NUMBER> --json reviews,comments,state gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/reviews ``` Repeat classification (Fix / Skip / Defer). Present a summary table: bot, file, verdict, one-line rationale. Apply fixes only for **Fix**; then: ```powershell git add -A git -c core.hooksPath=/dev/null commit -m "address bot review feedback" git -c core.hooksPath=/dev/null push gh pr checks <PR_NUMBER> --watch --interval 30 ``` If bots post **after** a green run (common on squash-merge), re-poll comments once more before merge. Do not merge with unaddressed **Fix** items on the release PR. ### 10. Merge and sync main ```powershell gh pr merge <PR_NUMBER> --squash --delete-branch git checkout main git fetch origin main git reset --hard origin/main ``` ### 11. Post-merge bot pass (before tag) On the merged release PR, fetch comments again in case bots reviewed the squash commit: ```powershell gh pr view <PR_NUMBER> --json comments,reviews,mergedAt gh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments ``` - **Fix** on `main`: commit directly on `main` only if policy allows; otherwise open a tiny follow-up PR. For release workflow, prefer a fast follow-up commit on `main` before tagging when the fix is trivial and release-blocking. - If a **Fix** requires re-tagging content, complete the fix, then tag (never move/delete an existing tag). ### 12. Tag (after merge only) Tags are protected — no force/delete. Tag must point at merged `main`: ```powershell git tag vX.Y.Z git -c core.hooksPath=/dev/null push origin vX.Y.Z ``` `v*` tag triggers **Build & Release** ([`.github/workflows/release.yml`](../../../.github/workflows/release.yml)). ### 13. Verify CI ```powershell gh run list --workflow=release.yml --limit 3 ``` Tell user: https://github.com/Mooshieblob1/MooshieUI/actions ### 14. Fallback If tag push fails or workflow does not start: ```powershell gh workflow run release.yml -f tag=vX.Y.Z ``` ### 15. Cleanup ```powershell git fetch --prune origin git -c core.hooksPath=/dev/null push origin --delete release/vX.Y.Z ``` Confirm no duplicate `release/v*` branches remain for this version. Prune stale local branches. ## About UI No manual About edit — version from `__APP_VERSION__`; release notes from GitHub Releases API at runtime. ## Checklist ``` - [ ] Stale/existing branches and open PRs reviewed; release/* cleaned up or continued intentionally - [ ] Bot comments triaged on open PRs + recent merges (Fix/Skip/Defer documented) - [ ] Pre-commit-check passed - [ ] Three version files match X.Y.Z - [ ] RELEASE_NOTES.md + CHANGELOG.md updated - [ ] cargo check + npm run build passed - [ ] Release PR merged to main - [ ] Post-merge bot pass completed (no unaddressed Fix items) - [ ] Tag vX.Y.Z pushed - [ ] Release workflow running - [ ] Remote release/vX.Y.Z branch deleted ``` ## Mistakes to avoid 1. Missing one of the three version files 2. Skipping `cargo check` (stale `Cargo.lock` breaks CI) 3. Tag before PR merge 4. `git` without `core.hooksPath=/dev/null` on Windows 5. Force-updating tags — use `workflow_dispatch` instead 6. Creating a second `release/vX.Y.Z` while an open PR already exists for the same version 7. Merging the release PR while another open PR has release-blocking bot **Fix** items still unresolved 8. Ignoring late bot comments posted after CI goes green 9. Adding `Co-Authored-By` trailers to commits, PR bodies, or comments — never attribute AI assistance in any git or GitHub output

{ "prompt": "# Release (MooshieUI)\n\nFull release path: **repo hygiene → pre-commit → version bump → changelog → build validation → PR → GlassWorm → bot triage (all relevant PRs) → merge → tag → CI**.\n\n## Inputs\n\n| Field | Default if omitted |\n|-------|-------------------|\n| Version `X.Y.Z` | Read `package.json`, patch+1 (no `v` prefix in files) |\n| Summary | `git log` since last `v*` tag |\n\n## Windows git (required)\n\n```text\ngit -c core.hooksPath=/dev/null ...\n```\n\nPre-commit hook hangs in PowerShell without this.\n\n## Workflow\n\n### 1. Repo hygiene — branches and open PRs [BLOCKING before new release branch]\n\nRefresh remotes, inventory branches/PRs, and resolve conflicts **before** creating `release/vX.Y.Z`.\n\n```powershell\ngit fetch --prune origin\ngit branch -vv\ngit branch -r\ngh pr list --state open --base main --json number,title,headRefName,updatedAt,isDraft\ngh api repos/Mooshieblob1/MooshieUI/branches?per_page=100 --jq '.[].name'\n```\n\n**Release / stale branch handling**\n\n| Situation | Action |\n|-----------|--------|\n| Remote `release/vX.Y.Z` already exists for **this** release | If PR is merged or abandoned: delete remote branch. If PR is still open and current: check out and continue on it (do not create a duplicate). |\n| Remote `release/v*` for an **older** version, PR merged | Delete remote branch: `git -c core.hooksPath=/dev/null push origin --delete release/vOLD` |\n| Remote `release/v*` with **closed** PR and no further work | Delete remote branch |\n| Local tracking branches for deleted remotes | `git fetch --prune` then delete stale locals |\n| Open PR targeting `main` that is superseded by this release | Close with a short comment, or merge first if it must ship in this release |\n| Open PR with failing **GlassWorm** or blocking CI | Fix on that branch/PR or close before cutting the release |\n\n**Do not** force-push `main` or protected tags. Do not delete branches that still have unmerged work the user intends to ship.\n\nReport a short table: branch/PR, status, action taken.\n\n### 2. Bot review sweep — open PRs and recent merges\n\nBefore version bump, triage bot feedback on PRs that could block or duplicate this release.\n\n**Bots to read** (non-exhaustive): `gemini-code-assist[bot]`, `copilot-pull-request-reviewer[bot]`, `github-actions[bot]` (only when comment contains a concrete fix).\n\n```powershell\n# Open PRs targeting main\ngh pr list --state open --base main --json number,title,headRefName\n\n# Per PR (replace N):\ngh pr view N --json reviews,comments,state,mergedAt\ngh api repos/Mooshieblob1/MooshieUI/pulls/N/comments\ngh api repos/Mooshieblob1/MooshieUI/pulls/N/reviews\n```\n\nAlso check **recently merged** PRs since the last `v*` tag (bots sometimes comment late or on squash-merge commits):\n\n```powershell\n$lastTag = git describe --tags --abbrev=0\ngh pr list --state merged --base main --limit 20 --json number,title,mergedAt\n```\n\nClassify every bot comment using [docs/BOT_REVIEW_TRIAGE.md](../../../docs/BOT_REVIEW_TRIAGE.md):\n\n| Verdict | Action |\n|---------|--------|\n| **Fix** | Correctness, safety, MIME mismatches, consistency — fix on that PR's branch if still open, or on `main`/release branch if merged and release-blocking |\n| **Skip** | Premature abstraction, nits, factually wrong bot claims — note rationale in release PR body or user summary |\n| **Defer** | Valid but not release-blocking — document for follow-up; do not block tag |\n\n**Release-blocking** bot findings on open PRs must be resolved (fix or explicit skip with verification) before creating the release PR. If a fix belongs on another open PR, land it there first or cherry-pick into the release branch.\n\n### 3. Pre-commit-check\n\nRun **pre-commit-check** on current tree. Fix blockers; re-run until ✅.\n\n### 4. Version bump (all three must match)\n\n| File | Field |\n|------|-------|\n| `package.json` | `\"version\": \"X.Y.Z\"` |\n| `src-tauri/Cargo.toml` | `version = \"X.Y.Z\"` under `[package]` |\n| `src-tauri/tauri.conf.json` | `\"version\": \"X.Y.Z\"` |\n\nVerify:\n\n```powershell\nSelect-String -Pattern '\"X.Y.Z\"|version = \"X.Y.Z\"' package.json, src-tauri/Cargo.toml, src-tauri/tauri.conf.json\n```\n\n### 5. Changelog files\n\nPrepend to **both** `RELEASE_NOTES.md` and `CHANGELOG.md`:\n\n```markdown\n## What's New in vX.Y.Z\n\n### Group title\n- Detail\n\n---\n\n## What's New in vPREVIOUS\n```\n\n`CHANGELOG.md`: new section goes directly under `# Changelog`.\n\n### 6. Build validation [BLOCKING]\n\n```powershell\ncargo check --manifest-path src-tauri/Cargo.toml\ncargo check --manifest-path src-tauri/Cargo.toml --no-default-features --features server\ncargo test --manifest-path src-tauri/Cargo.toml\nnpm run build\n```\n\n### 7. Release branch and PR\n\nConfirm step 1: no conflicting `release/vX.Y.Z` on remote (unless intentionally continuing that PR).\n\n```powershell\ngit checkout main\ngit pull origin main\ngit checkout -b release/vX.Y.Z\ngit add -A\ngit -c core.hooksPath=/dev/null commit -m \"vX.Y.Z: Short summary\"\ngit -c core.hooksPath=/dev/null push -u origin release/vX.Y.Z\ngh pr create --base main --head release/vX.Y.Z --title \"vX.Y.Z: Short summary\" --body \"<bullet list of changes; note any bot triage from steps 1-2>\"\n```\n\n### 8. CI\n\n```powershell\ngh pr checks <PR_NUMBER> --watch --interval 30\n```\n\nWait for **GlassWorm Infection Audit** SUCCESS (5 min timeout).\n\n### 9. Bot review triage — release PR (and late comments)\n\nWait ~60s after CI green. Re-fetch **all** bot threads on the release PR:\n\n```powershell\ngh pr view <PR_NUMBER> --json reviews,comments,state\ngh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments\ngh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/reviews\n```\n\nRepeat classification (Fix / Skip / Defer). Present a summary table: bot, file, verdict, one-line rationale.\n\nApply fixes only for **Fix**; then:\n\n```powershell\ngit add -A\ngit -c core.hooksPath=/dev/null commit -m \"address bot review feedback\"\ngit -c core.hooksPath=/dev/null push\ngh pr checks <PR_NUMBER> --watch --interval 30\n```\n\nIf bots post **after** a green run (common on squash-merge), re-poll comments once more before merge. Do not merge with unaddressed **Fix** items on the release PR.\n\n### 10. Merge and sync main\n\n```powershell\ngh pr merge <PR_NUMBER> --squash --delete-branch\ngit checkout main\ngit fetch origin main\ngit reset --hard origin/main\n```\n\n### 11. Post-merge bot pass (before tag)\n\nOn the merged release PR, fetch comments again in case bots reviewed the squash commit:\n\n```powershell\ngh pr view <PR_NUMBER> --json comments,reviews,mergedAt\ngh api repos/Mooshieblob1/MooshieUI/pulls/<PR_NUMBER>/comments\n```\n\n- **Fix** on `main`: commit directly on `main` only if policy allows; otherwise open a tiny follow-up PR. For release workflow, prefer a fast follow-up commit on `main` before tagging when the fix is trivial and release-blocking.\n- If a **Fix** requires re-tagging content, complete the fix, then tag (never move/delete an existing tag).\n\n### 12. Tag (after merge only)\n\nTags are protected — no force/delete. Tag must point at merged `main`:\n\n```powershell\ngit tag vX.Y.Z\ngit -c core.hooksPath=/dev/null push origin vX.Y.Z\n```\n\n`v*` tag triggers **Build & Release** ([`.github/workflows/release.yml`](../../../.github/workflows/release.yml)).\n\n### 13. Verify CI\n\n```powershell\ngh run list --workflow=release.yml --limit 3\n```\n\nTell user: https://github.com/Mooshieblob1/MooshieUI/actions\n\n### 14. Fallback\n\nIf tag push fails or workflow does not start:\n\n```powershell\ngh workflow run release.yml -f tag=vX.Y.Z\n```\n\n### 15. Cleanup\n\n```powershell\ngit fetch --prune origin\ngit -c core.hooksPath=/dev/null push origin --delete release/vX.Y.Z\n```\n\nConfirm no duplicate `release/v*` branches remain for this version. Prune stale local branches.\n\n## About UI\n\nNo manual About edit — version from `__APP_VERSION__`; release notes from GitHub Releases API at runtime.\n\n## Checklist\n\n```\n- [ ] Stale/existing branches and open PRs reviewed; release/* cleaned up or continued intentionally\n- [ ] Bot comments triaged on open PRs + recent merges (Fix/Skip/Defer documented)\n- [ ] Pre-commit-check passed\n- [ ] Three version files match X.Y.Z\n- [ ] RELEASE_NOTES.md + CHANGELOG.md updated\n- [ ] cargo check + npm run build passed\n- [ ] Release PR merged to main\n- [ ] Post-merge bot pass completed (no unaddressed Fix items)\n- [ ] Tag vX.Y.Z pushed\n- [ ] Release workflow running\n- [ ] Remote release/vX.Y.Z branch deleted\n```\n\n## Mistakes to avoid\n\n1. Missing one of the three version files\n2. Skipping `cargo check` (stale `Cargo.lock` breaks CI)\n3. Tag before PR merge\n4. `git` without `core.hooksPath=/dev/null` on Windows\n5. Force-updating tags — use `workflow_dispatch` instead\n6. Creating a second `release/vX.Y.Z` while an open PR already exists for the same version\n7. Merging the release PR while another open PR has release-blocking bot **Fix** items still unresolved\n8. Ignoring late bot comments posted after CI goes green\n9. Adding `Co-Authored-By` trailers to commits, PR bodies, or comments — never attribute AI assistance in any git or GitHub output", "variables": [], "notes": "Cut a new MooshieUI release — bump versions, update release notes, validate, tag, and push Arguments: Version number (e.g. 0.4.3) and a brief summary of changes.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Mooshieblob1/MooshieUI", "path": ".github/prompts/release.prompt.md", "ref": "3317a5e167fecb8b7a35727bad4996197bd29d90", "url": "https://github.com/Mooshieblob1/MooshieUI/blob/3317a5e167fecb8b7a35727bad4996197bd29d90/.github/prompts/release.prompt.md", "key": "Mooshieblob1/MooshieUI/.github/prompts/release.prompt.md" } } }

release

About