release-version

name	release-version
description	Release a new r-shell version and draft a GitHub release. Use when: releasing, publishing, bumping version, tagging, drafting release, creating release notes, gh release create, version bump, patch release, minor release, major release.
argument-hint	bump type: patch | minor | major

Release New Version & Draft GitHub Release

Bumps the project version across all config files, updates the CHANGELOG, pushes a tag, and creates a draft GitHub release using gh.

When to Use

• Releasing a new patch, minor, or major version of r-shell
• Creating a GitHub draft release with changelog notes
• Tagging a new version and pushing to origin

Procedure

1. Determine Bump Type

Ask (or infer from the argument) whether this is a patch, minor, or major bump:

Type	When	Example
patch	Bug fixes, small tweaks	1.2.3 → 1.2.4
minor	New features, backward-compatible	1.2.3 → 1.3.0
major	Breaking changes	1.2.3 → 2.0.0

2. Run the Version Bump Script

# Replace <type> with patch, minor, or major
pnpm run version:<type>

This updates all four version locations atomically and creates a git commit:

• package.json
• src-tauri/Cargo.toml
• src-tauri/Cargo.lock
• src-tauri/tauri.conf.json
• CHANGELOG.md (adds a skeleton section)

Read the new version from package.json:

node -p "require('./package.json').version"

3. Update CHANGELOG.md

First, get the actual commits since the previous tag. Find the previous tag and list every commit:

PREV_TAG=$(git tag --sort=-v:refname | sed -n '2p')   # second-newest tag
git log "${PREV_TAG}..HEAD" --oneline --no-merges

⚠️ CRITICAL — Do NOT fabricate changelog entries. Every bullet point MUST correspond to a commit in the output above. Do not copy bullets from older versions, do not invent features, and do not summarize the whole project history.

Open CHANGELOG.md and fill in the new version section that the script created. Replace the placeholder lines with actual release notes derived strictly from the commit list, grouped under:

• ### Added — new features (feat: commits)
• ### Changed — modifications to existing behavior (refactor:, perf: commits)
• ### Fixed — bug fixes (fix: commits)
• ### Removed — anything deleted (omit section if empty)

Use emoji prefixes consistent with existing entries (e.g. 🔌, 🖥️, 🐛). Add a release headline as the first paragraph after the version header (see existing entries for the pattern: ### 🔖 R-Shell X.Y — Codename).

After editing, amend the commit to include the updated CHANGELOG:

git add CHANGELOG.md
git commit --amend --no-edit

4. Create and Push the Git Tag

VERSION=$(node -p "require('./package.json').version")
git tag "v${VERSION}"
git push origin main
git push origin "v${VERSION}"

5. Extract Release Notes from CHANGELOG

Parse the new version's section from CHANGELOG.md and write it to a temp file (shell variable interpolation silently truncates multiline content, so always use a file):

VERSION=$(node -p "require('./package.json').version")
NOTES_FILE=$(mktemp /tmp/release-notes-XXXXXX.md)
awk "/^## \[${VERSION}\]/{found=1; next} found && /^## /{exit} found{print}" CHANGELOG.md > "${NOTES_FILE}"

Verify the file is non-empty before proceeding:

cat "${NOTES_FILE}"
# If empty, the awk pattern didn't match — check CHANGELOG.md header format is exactly ## [X.Y.Z]
wc -l "${NOTES_FILE}"

If the file is empty, do NOT continue — fix the CHANGELOG header format first.

6. Draft the GitHub Release

Use --notes-file (not --notes) to pass multiline content reliably:

VERSION=$(node -p "require('./package.json').version")

gh release create "v${VERSION}" \
  --title "v${VERSION}" \
  --notes-file "${NOTES_FILE}" \
  --draft \
  --repo GOODBOY008/r-shell

rm -f "${NOTES_FILE}"

The --draft flag keeps the release hidden until you publish it manually on GitHub. Remove --draft only if you want to publish immediately.

7. Verify

VERSION=$(node -p "require('./package.json').version")
gh release view "v${VERSION}" --repo GOODBOY008/r-shell

Check the output includes the release body text (not just "See the assets…"). If the body is empty, the notes file was empty or the awk pattern didn't match — re-run step 5 to debug, then use gh release edit "v${VERSION}" --notes-file <file> --repo GOODBOY008/r-shell to fix it.

Decision Points

• Changelog already accurate? Skip step 3 and the amend.
• Want to publish immediately instead of drafting? Drop --draft in step 6.
• Attaching build artifacts? Add file paths after the tag in gh release create: gh release create "v${VERSION}" ./dist/*.dmg ./dist/*.exe --draft ...
• Pre-release? Append --prerelease to the gh release create command.

Prerequisites

• gh CLI authenticated (gh auth status)
• pnpm installed
• Git remote origin points to GOODBOY008/r-shell
• Clean working tree before starting (git status)