Menu
Step through versioning, tagging, and verification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| title | Release flow |
| description | Step through versioning, tagging, and verification |
| name | release |
Confirm the repo is on main and clean. Keep changes aligned with OpenCode primitives like .opencode, opencode.json, skills, and plugins when relevant.
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 the version bump into main. Make sure no secrets or credentials are committed.
Create and push the tag to trigger the Release App workflow.
git tag vX.Y.Z
git push origin vX.Y.Z
If a tag needs a rerun, dispatch the workflow.
gh workflow run "Release App" --repo different-ai/openwork -f tag=vX.Y.Z
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
Manage OpenWork inference model aliases, openwork model overlays, discounts, validation, and automated base model refreshes from models.dev. Use when adding, removing, discounting, auditing, or updating OpenWork models, including requests like "update the models" that should trigger the GitHub update-models workflow and report when its PR merges.
create a fraimz, make fraimz, prove it works, frame proof, PR proof, validate experience, e2e evidence, fraimz.html. The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html. Use whenever a task ends with "please create a fraimz" or any change needs end-to-end proof.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Daytona cloud instance, Den server, OpenWork Cloud, Marketplace onboarding, desktop plus cloud e2e, frame proof. Use when launching, validating, or recording Daytona cloud/Den flows.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Electron and Den, desktop plus cloud, two-sandbox e2e, cloud auth, marketplace, org policy, worker proxy, provider sync, desktop handoff. Validate Electron against a Daytona Den server with unified proof.