/wbRelease — Command Hub

/wbRelease manages the full release workflow: version bumping, changelog generation, git tagging, and pre-publish validation. It coordinates the transition from development HEAD to a versioned artifact so that everything /wbPublish and /wbBroadcast depend on is in place before a single package hits npm.

🎯 Strategic Position

/wbRelease sits between verification and publication. It is the gate you pass after the audit says "ship" and before you actually push. Unlike /wbPublish which executes the final npm publish, /wbRelease prepares the entire monorepo — unpicking workspace protocols, bumping versions across the dependency graph, and generating the changelog — so that what goes out is internally coherent.

• When an audit and test suite pass — run /wbRelease --dry-run to preview, then /wbRelease for real.
• After /wbPublish succeeds — run /wbRelease --restore to restore workspace protocols.
• For pre-release experiments — use --prerelease=beta for 1.5.0-beta.0 style bumps.

🛠️ Operating Modes

Mode	Trigger	Output
Dry-run	/wbRelease <monorepo-root>/ --dry-run	Full preview of what will change, no mutations
Standard	/wbRelease <monorepo-root>/	Version bumps, changelog, git tag, workspace protocol unpick
Restore	/wbRelease <monorepo-root>/ --restore	Restores workspace: protocols after publish
Pre-release	/wbRelease <monorepo-root>/ --prerelease=beta	Beta/alpha/rc version with pre-release tag

✅ What a useful release contains

1. A dry-run preview first — never release blind.
2. A version bump calculated from conventional commits — fix: → patch, feat: → minor, feat!: / BREAKING CHANGE: → major.
3. A full changelog synthesized from recent reports.
4. The topological publish order for all sub-packages.
5. A restore instruction so the next pnpm install uses local packages, not npm.

🚫 What it cannot do

Not this	Use instead
Publish to npm	/wbPublish
Deploy to production	/wbDeploy
Announce a release	/wbBroadcast
Verify code quality before release	/wbAudit
Test before release	/wbTest

It refuses when: audit has BLOCKER findings, tests fail, no packages have changes since last release, the working tree is dirty, or the current branch is not the release branch.

📚 Reading Order

1. ELI5 — the one-paragraph mental model.
2. Practical — step-by-step on a real project.
3. Expert — architecture, edge cases, and when NOT to use.
4. Examples · Part 1 · Part 2 — annotated transcripts.
5. Exhaustive simulation · Live demo.

🔗 Related

• wbRelease.md — the command reference this hub orients you around.
• /wbPublish — publishes the prepared release to npm.
• /wbBroadcast — announces the release.
• /wbDeploy — deploys apps (not packages).
• /wbAudit — the gate you must pass before releasing.

Quick Reference

/wbRelease <monorepo-root>/ --dry-run            # preview everything first
/wbRelease <monorepo-root>/                       # real release
/wbRelease <monorepo-root>/ --prerelease=beta     # pre-release
/wbRelease <monorepo-root>/ --restore             # restore after publish

---

---

← Home · Commands · Install | wb-flow on npm · flow.wbc-ui.com · wi-bg.com