Skip to content

ci: align release workflow with sibling Otto plugins - #3

Closed
sdziupin wants to merge 1 commit into
feat/opencode-commandcode-36ebfrom
feat/release-workflow-36eb
Closed

sdziupin wants to merge 1 commit into
feat/opencode-commandcode-36ebfrom
feat/release-workflow-36eb

Conversation

@sdziupin

@sdziupin sdziupin commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Aligns the release automation with @otto-assistant/opencode-claude and @otto-assistant/opencode-cursor.

Changes

  • .github/workflows/release.yml — same flow as siblings:
    • workflow_dispatch inputs: version / bump / dry_run
    • Show version info step
    • bun install → test → build
    • Commit + tag vX.Y.Z, push to main
    • npm publish (skipped on dry run)
    • GitHub Release (draft on dry run)
    • Optional Discord notification via DISCORD_WEBHOOK_URL (branded opencode-commandcode)
  • scripts/update-plugin.sh — full pin-refresh helper like the sibling plugins (--dry-run, npm latest check, rebase, restart opencode serve)

Secrets needed

  • NPM_TOKEN (required for publish)
  • DISCORD_WEBHOOK_URL (optional)

Stacked on feat/opencode-commandcode-36eb.

Open in Web Open in Cursor 

Match opencode-claude/cursor release.yml: version info step, Discord
notification (optional webhook), and full update-plugin.sh pin refresh.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant