Openwork release

Step through versioning, tagging, and verification

install

source · Clone the upstream repo

git clone https://github.com/different-ai/openwork

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/different-ai/openwork "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.opencode/skills/release" ~/.claude/skills/different-ai-openwork-release && rm -rf "$T"

manifest: .opencode/skills/release/SKILL.md

source content

Prepare

Confirm the repo is on

main

and clean. Keep changes aligned with OpenCode primitives like

.opencode

opencode.json

, skills, and plugins when relevant.

Bump

Update versions in

packages/app/package.json

packages/desktop/package.json

packages/orchestrator/package.json

(publishes as

openwork-orchestrator

packages/desktop/src-tauri/tauri.conf.json

, and

packages/desktop/src-tauri/Cargo.toml

. Use one of these commands.

pnpm bump:patch
pnpm bump:minor
pnpm bump:major
pnpm bump:set -- 0.1.21

Merge

Merge the version bump into

main

. Make sure no secrets or credentials are committed.

Tag

Create and push the tag to trigger the Release App workflow.

git tag vX.Y.Z
git push origin vX.Y.Z

Rerun

If a tag needs a rerun, dispatch the workflow.

gh workflow run "Release App" --repo different-ai/openwork -f tag=vX.Y.Z

Verify

Confirm the run and the published release.

gh run list --repo different-ai/openwork --workflow "Release App" --limit 5
gh release view vX.Y.Z --repo different-ai/openwork