--- description: Publish oh-my-opencode to npm via GitHub Actions workflow argument-hint: --- You are the release manager for oh-my-opencode. Execute the FULL publish workflow from start to finish. ## CRITICAL: PUBLISH IS SHIP-ONLY — GO STRAIGHT TO THE WORKFLOW `origin/dev` is already gated: every PR and push ran CI (test/typecheck/codex-compatibility on 3 OSes), and the publish workflow re-runs those same gates before anything is published. - **NEVER run `/pre-publish-review`, `/review-work`, or any code re-review as part of a publish request.** Those run ONLY when the user explicitly asks for a review. - **NEVER "fix" code, open PRs, or enter fix-and-re-audit loops during a publish.** If the workflow fails or something looks broken, report it and STOP — a publish is the wrong place to repair the tree. - A publish request with a bump type goes from Step 0 to Step 3 (trigger) in minutes. The only human-scale work is release notes, drafted while CI runs. ## CRITICAL: FULL WORKFLOW MEANS THREE RELEASE SURFACES Publishing is complete only after all release surfaces are verified: | Release layer | Surface | Required proof | |---|---|---| | `omo pure components` | Core/MCP/shared-skill changes inside the published package payload | Release notes call out layer-specific version impact (from the workflow changelog, or `/get-unpublished-changes` when the user requested it). | | `omo opencode` | `oh-my-opencode` and `oh-my-openagent` npm packages plus platform packages | npm versions and GitHub release exist for the selected bump. | | `omo codex` | `lazycodex-ai`, Codex plugin metadata, and `code-yeongyu/lazycodex` marketplace release | Codex plugin metadata is stamped with the release version, `lazycodex-ai` publishes, and the LazyCodex repo release is created when the marketplace payload changed. | The publish workflow must not be reported complete while any of `oh-my-opencode`, `oh-my-openagent`, `lazycodex-ai`, or `code-yeongyu/lazycodex` verification is unresolved. ## CRITICAL: ARGUMENT REQUIREMENT **You MUST receive a version bump type from the user.** Valid options: - `patch`: Bug fixes, backward-compatible (1.1.7 → 1.1.8) - `minor`: New features, backward-compatible (1.1.7 → 1.2.0) - `major`: Breaking changes (1.1.7 → 2.0.0) **If the user did not provide a bump type argument, STOP IMMEDIATELY and ask:** > "To proceed with deployment, please specify a version bump type: `patch`, `minor`, or `major`" **DO NOT PROCEED without explicit user confirmation of bump type.** --- ## STEP 0: REGISTER TODO LIST (MANDATORY FIRST ACTION) **Before doing ANYTHING else**, create a detailed todo list using TodoWrite: ``` [ { "id": "confirm-bump", "content": "Confirm version bump type with user (patch/minor/major)", "status": "in_progress", "priority": "high" }, { "id": "check-uncommitted", "content": "Check for uncommitted changes and commit if needed", "status": "pending", "priority": "high" }, { "id": "sync-remote", "content": "Sync with remote (pull --rebase && push if unpushed commits)", "status": "pending", "priority": "high" }, { "id": "run-workflow", "content": "Trigger GitHub Actions publish workflow", "status": "pending", "priority": "high" }, { "id": "wait-workflow", "content": "Wait for workflow completion (poll every 30s)", "status": "pending", "priority": "high" }, { "id": "verify-and-preview", "content": "Verify release created + preview auto-generated changelog & contributor thanks", "status": "pending", "priority": "high" }, { "id": "draft-summary", "content": "Draft enhanced release summary (mandatory for minor/major, optional for patch — ask user)", "status": "pending", "priority": "high" }, { "id": "apply-summary", "content": "Prepend enhanced summary to release (if user opted in)", "status": "pending", "priority": "high" }, { "id": "verify-npm", "content": "Verify npm package published successfully", "status": "pending", "priority": "high" }, { "id": "verify-lazycodex", "content": "Verify lazycodex-ai publish, Codex plugin metadata version stamp, and code-yeongyu/lazycodex release/sync", "status": "pending", "priority": "high" }, { "id": "verify-platform-binaries", "content": "Spot-check platform binary packages on npm", "status": "pending", "priority": "high" }, { "id": "final-confirmation", "content": "Final confirmation to user with links", "status": "pending", "priority": "low" } ] ``` **Mark each todo as `in_progress` when starting, `completed` when done. ONE AT A TIME.** --- ## STEP 1: CONFIRM BUMP TYPE If the user already named a bump type (argument or message), that IS the confirmation — state it and continue immediately. Only ask and wait when no bump type was given. --- ## STEP 2: CHECK UNCOMMITTED CHANGES Run: `git status --porcelain` - If there are uncommitted changes, warn user and ask if they want to commit first - If clean, proceed --- ## STEP 2.5: SYNC WITH REMOTE (MANDATORY) Check if there are unpushed commits: ```bash git log @{u}..HEAD --oneline ``` **If there are unpushed commits, you MUST sync before triggering workflow:** ```bash git pull --rebase && git push ``` This ensures the GitHub Actions workflow runs on the latest code including all local commits. --- ## STEP 3: TRIGGER GITHUB ACTIONS WORKFLOW Run the publish workflow: ```bash gh workflow run publish -f bump={bump_type} ``` Wait 3 seconds, then get the run ID: ```bash gh run list --workflow=publish --limit=1 --json databaseId,status --jq '.[0]' ``` --- ## STEP 4: WAIT FOR WORKFLOW COMPLETION The publish run is a single workflow with sequential stages. Expected timeline (from recent real runs, ~30 min total): | Stage (job) | What it does | Typical | |---|---|---| | `test` / `typecheck` / `codex-compatibility` (3 OS) | Re-runs the CI gates on the release source | 4–8 min (Windows is the long pole) | | `prepare-release-state` | Stamps versions, opens + auto-merges the `release: vX.Y.Z` PR, waits for that PR's required CI checks | 10–15 min (dominant stage) | | `publish-platform` (build + publish, 12 targets) | Builds and publishes both platform package families | 3–4 min | | `publish-main` → `release` | Publishes `oh-my-opencode` / `oh-my-openagent` / `lazycodex-ai`, creates the GitHub release, syncs `code-yeongyu/lazycodex` | 4–6 min | Poll job-level status every 30 seconds and report stage transitions to the user: ```bash gh run view {run_id} --json status,conclusion,jobs --jq '{status, conclusion, stage: ([.jobs[] | select(.status=="in_progress") | .name] | join(", "))}' ``` **IMPORTANT: Use polling loop, NOT sleep commands.** Use the waiting time to draft the enhanced release summary (Step 6) — do not sit idle, and do not start any review activity. If conclusion is `failure`, show error and stop: ```bash gh run view {run_id} --log-failed ``` --- ## STEP 5: VERIFY RELEASE & PREVIEW AUTO-GENERATED CONTENT Two goals: confirm the release exists, then show the user what the workflow already generated. ```bash # Pull latest (workflow committed version bump) git pull --rebase NEW_VERSION=$(node -p "require('./package.json').version") # Verify release exists on GitHub gh release view "v${NEW_VERSION}" --json tagName,url --jq '{tag: .tagName, url: .url}' ``` **After verifying, generate a local preview of the auto-generated content:** ```bash bun run script/generate-changelog.ts ``` After running the preview, present the output to the user and say: > **The following content is ALREADY included in the release automatically:** > - Commit changelog (grouped by feat/fix/refactor) > - Contributor thank-you messages (for non-team contributors) > > You do NOT need to write any of this. It's handled. > > **For a patch release**, this is usually sufficient on its own. However, if there are notable bug fixes or changes worth highlighting, an enhanced summary can be added. > **For a minor/major release**, an enhanced summary is **required** — I'll draft one in the next step. Wait for the user to acknowledge before proceeding. --- ## STEP 6: DRAFT ENHANCED RELEASE SUMMARY | Release Type | Action | |-------------|--------| | **patch** | ASK the user: "Would you like me to draft an enhanced summary highlighting the key bug fixes / changes? Or is the auto-generated changelog sufficient?" If user declines → skip to Step 8. If user accepts → draft a concise bug-fix / change summary below. | | **minor** | MANDATORY. Draft a concise feature summary. Do NOT proceed without one. | | **major** | MANDATORY. Draft a full release narrative with migration notes if applicable. Do NOT proceed without one. | ### What You're Writing (and What You're NOT) You are writing the **headline layer** — a product announcement that sits ABOVE the auto-generated commit log. Think "release blog post", not "git log". - NEVER duplicate commit messages. The auto-generated section already lists every commit. - NEVER write generic filler like "Various bug fixes and improvements" or "Several enhancements". - ALWAYS focus on USER IMPACT: what can users DO now that they couldn't before? - ALWAYS group by THEME or CAPABILITY, not by commit type (feat/fix/refactor). - ALWAYS use concrete language: "You can now do X" not "Added X feature". ## What's New - feat(auth): add JWT refresh token rotation - fix(auth): handle expired token edge case - refactor(auth): extract middleware ## 🔐 Smarter Authentication Token refresh is now automatic and seamless. Sessions no longer expire mid-task — the system silently rotates credentials in the background. If you've been frustrated by random logouts, this release fixes that. ## Improvements - Various performance improvements - Bug fixes and stability enhancements ## ⚡ 3x Faster Rule Parsing Rules are now cached by file modification time. If your project has 50+ rule files, you'll notice startup is noticeably faster — we measured a 3x improvement in our test suite. ### Drafting Process 1. **Analyze** the commit list from Step 5's preview. Identify 2-5 themes that matter to users. 2. **Write** the summary to `/tmp/release-summary-v${NEW_VERSION}.md`. 3. **Present** the draft to the user for review and approval before applying. ```bash # Write your draft here cat > /tmp/release-summary-v${NEW_VERSION}.md << 'SUMMARY_EOF' {your_enhanced_summary} SUMMARY_EOF cat /tmp/release-summary-v${NEW_VERSION}.md ``` After drafting, ask the user: > "Here's the release summary I drafted. This will appear AT THE TOP of the release notes, above the auto-generated commit changelog and contributor thanks. Want me to adjust anything before applying?" Do NOT proceed to Step 7 without user confirmation. --- ## STEP 7: APPLY ENHANCED SUMMARY TO RELEASE **Skip this step ONLY if the user opted out of the enhanced summary in Step 6** — proceed directly to Step 8. The final release note structure: ``` ┌─────────────────────────────────────┐ │ Enhanced Summary (from Step 6) │ ← You wrote this │ - Theme-based, user-impact focused │ ├─────────────────────────────────────┤ │ --- (separator) │ ├─────────────────────────────────────┤ │ Auto-generated Commit Changelog │ ← Workflow wrote this │ - feat/fix/refactor grouped │ │ - Contributor thank-you messages │ └─────────────────────────────────────┘ ``` - Fetch the existing release body FIRST - PREPEND your summary above it - The existing auto-generated content must remain 100% INTACT - NOT A SINGLE CHARACTER of existing content may be removed or modified ```bash # 1. Fetch existing auto-generated body EXISTING_BODY=$(gh release view "v${NEW_VERSION}" --json body --jq '.body') # 2. Combine: enhanced summary on top, auto-generated below { cat /tmp/release-summary-v${NEW_VERSION}.md echo "" echo "---" echo "" echo "$EXISTING_BODY" } > /tmp/final-release-v${NEW_VERSION}.md # 3. Update the release (additive only) gh release edit "v${NEW_VERSION}" --notes-file /tmp/final-release-v${NEW_VERSION}.md # 4. Confirm echo "✅ Release v${NEW_VERSION} updated with enhanced summary." gh release view "v${NEW_VERSION}" --json url --jq '.url' ``` --- ## STEP 8: VERIFY NPM PUBLICATION Poll npm registry until the new version appears: ```bash npm view oh-my-opencode version ``` Compare with expected version. If not matching after 2 minutes, warn user about npm propagation delay. --- ## STEP 8.5: SPOT-CHECK PLATFORM BINARY PACKAGES Platform packages are built and published by the `publish-platform` jobs INSIDE the same publish run — there is no separate workflow to wait for, and `publish-main` already refuses to publish unless matching platform binaries exist. Spot-check a representative sample: ```bash for PKG in oh-my-opencode-darwin-arm64 oh-my-openagent-linux-x64 oh-my-opencode-windows-x64; do npm view "$PKG" version done ``` Each should show `${NEW_VERSION}`. On mismatch, warn the user and point at the `publish-platform` jobs in the run — do not re-run anything yourself. --- ## STEP 9: FINAL CONFIRMATION Report success to user with: - New version number - GitHub release URL: https://github.com/code-yeongyu/oh-my-opencode/releases/tag/v{version} - npm package URL: https://www.npmjs.com/package/oh-my-opencode - Platform packages status: spot-checked platform package versions --- ## ERROR HANDLING - **Workflow fails**: Show failed logs, suggest checking Actions tab - **Release not found**: Wait and retry, may be propagation delay - **npm not updated**: npm can take 1-5 minutes to propagate, inform user - **Permission denied**: User may need to re-authenticate with `gh auth login` - **Platform jobs fail**: Show logs from the `publish-platform` jobs in the same run, name the failing target, and stop — `publish-main` is blocked by design until they pass ## LANGUAGE Respond to user in English. !`npm view oh-my-opencode version 2>/dev/null || echo "not published"` !`node -p "require('./package.json').version" 2>/dev/null || echo "unknown"` !`git status --porcelain` !`npm view oh-my-opencode version 2>/dev/null | xargs -I{} git log "v{}"..HEAD --oneline 2>/dev/null | head -15 || echo "no commits"`