publish

You are the release manager for oh-my-opencode. Execute the FULL publish workflow from start to finish.

CRITICAL: FULL WORKFLOW MEANS DISCORD TOO

Publishing is not complete until the Discord release announcement has been attempted.

• DO NOT stop after creating the GitHub release.
• DO NOT stop after drafting or applying release notes.
• DO NOT wait for a second user acknowledgement if the user already confirmed the publish.
• After the release notes are finalized, immediately run Step 7.5 and post to Discord.
• If Discord posting fails after authentication/retry, report the failure clearly and continue the remaining verification steps. A skipped Discord step is a workflow failure.

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 all release types)", "status": "pending", "priority": "high" },
  { "id": "apply-summary", "content": "Prepend enhanced summary to release", "status": "pending", "priority": "high" },
  { "id": "discord-announce", "content": "MANDATORY: post release announcement to Discord channel immediately after release notes are finalized", "status": "pending", "priority": "high" },
  { "id": "verify-npm", "content": "Verify npm package published successfully", "status": "pending", "priority": "high" },
  { "id": "wait-platform-workflow", "content": "Wait for publish-platform workflow completion", "status": "pending", "priority": "high" },
  { "id": "verify-platform-binaries", "content": "Verify all 7 platform binary packages published", "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 bump type provided as argument, confirm with user:

"Version bump type: {bump}. Proceed? (y/n)"

Wait for user confirmation before proceeding.

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:

git log origin/master..HEAD --oneline

If there are unpushed commits, you MUST sync before triggering workflow:

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:

gh workflow run publish -f bump={bump_type}

Wait 3 seconds, then get the run ID:

gh run list --workflow=publish --limit=1 --json databaseId,status --jq '.[0]'

STEP 4: WAIT FOR WORKFLOW COMPLETION

Poll workflow status every 30 seconds until completion:

gh run view {run_id} --json status,conclusion --jq '{status: .status, conclusion: .conclusion}'

Status flow: queued → in_progress → completed

IMPORTANT: Use polling loop, NOT sleep commands.

If conclusion is failure, show error and stop:

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.

# 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:

bun run script/generate-changelog.ts

<agent-instruction> 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 all release types, an enhanced summary is required — I'll draft one in the next step.

Wait for the user to acknowledge before proceeding.

If the user already confirmed the publish workflow and did not explicitly ask to review the generated changelog before release-note editing, treat the publish confirmation as sufficient acknowledgement and continue. Do not end the assistant turn here. </agent-instruction>

STEP 6: DRAFT ENHANCED RELEASE SUMMARY

<decision-gate>

| Release Type | Action | |-------------|--------| | patch | MANDATORY. Draft a concise bug-fix / change summary. Do NOT proceed without one. | | 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. |

</decision-gate>

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".

<rules>

• 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".

</rules>

<examples> <bad title="Commit regurgitation — DO NOT do this">

What's New

• feat(auth): add JWT refresh token rotation
• fix(auth): handle expired token edge case
• refactor(auth): extract middleware

</bad>

<good title="User-impact narrative — DO this">

🔐 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. </good>

<bad title="Vague filler — DO NOT do this">

Improvements

• Various performance improvements
• Bug fixes and stability enhancements

</bad>

<good title="Specific and measurable — DO this">

⚡ 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. </good>