openwork-orchestrator-npm-publish

Quick usage (already configured)

1. Ensure you are on the default branch and the tree is clean.
2. Bump versions via the shared release bump (this keeps openwork-orchestrator aligned with the app/desktop release).

pnpm bump:patch
# or: pnpm bump:minor
# or: pnpm bump:major
# or: pnpm bump:set -- X.Y.Z

3. Commit the bump.
4. Preferred: publish via the “Release App” GitHub Actions workflow by tagging vX.Y.Z.

Manual recovery path (sidecars + npm) below.

pnpm --filter openwork-orchestrator build:sidecars
gh release create openwork-orchestrator-vX.Y.Z packages/orchestrator/dist/sidecars/* \
  --repo different-ai/openwork \
  --title "openwork-orchestrator vX.Y.Z sidecars" \
  --notes "Sidecar binaries and manifest for openwork-orchestrator vX.Y.Z"

5. Build openwork-orchestrator binaries for all supported platforms.

pnpm --filter openwork-orchestrator build:bin:all

6. Publish openwork-orchestrator as a meta package + platform packages (optionalDependencies).

node packages/orchestrator/scripts/publish-npm.mjs

7. Verify the published version.

npm view openwork-orchestrator version

Scripted publish

./.opencode/skills/openwork-orchestrator-npm-publish/scripts/publish-openwork-orchestrator.sh

First-time setup (if not configured)

Authenticate with npm before publishing.

npm login

Alternatively, export an npm token in your environment (see .env.example).

Notes

• openwork-orchestrator is published as:
  • openwork-orchestrator (wrapper + optionalDependencies)
  • openwork-orchestrator-darwin-arm64, openwork-orchestrator-darwin-x64, openwork-orchestrator-linux-arm64, openwork-orchestrator-linux-x64, openwork-orchestrator-windows-x64 (platform binaries)
• openwork-orchestrator is versioned in lockstep with OpenWork app/desktop releases.
• openwork-orchestrator downloads sidecars from openwork-orchestrator-vX.Y.Z release assets by default.