openwork/.opencode/commands/release.md at 47db4e39e3fb312fcb198ecdf786d87ac2b6cc76

mirror of https://github.com/different-ai/openwork synced 2026-04-26 01:25:10 +02:00

Files

ben 6284b581f7 chore: rename openwrk to openwork-orchestrator (#573 )

* chore(orchestrator): rename openwrk to openwork-orchestrator

Rename the host package and internal references from openwrk to openwork-orchestrator, and expose the CLI as 'openwork'.

Update desktop/UI runtime wiring, release workflows, and docs; bundle the Tauri sidecar as 'openwork-orchestrator' to avoid Cargo package name collisions.

* chore: keep orchestrator publish script executable

* chore: update pnpm lockfile

* chore: sync lockfile with orchestrator deps

* docs: update orchestrator usage + release notes

Document that openwork-orchestrator installs the 'openwork' CLI, update release command wording, and remove obsolete workflow branch trigger.

2026-02-15 14:24:42 -08:00

1.0 KiB

Raw Blame History

description

description
Run the OpenWork release flow

You are running the OpenWork release flow in this repo.

Arguments: $ARGUMENTS

If empty, default to a patch release.
If set to minor or major, use that bump type.

Do the following, in order, and stop on any failure:

Sync dev and ensure the working tree is clean.
Bump app/desktop versions using pnpm bump:$ARGUMENTS (or pnpm bump:patch if empty).
If any dependencies were pinned or changed, run pnpm install --lockfile-only.
Run pnpm release:review and resolve any mismatches.
Tag and push: git tag vX.Y.Z and git push origin vX.Y.Z, then git push origin dev.
Watch the Release App GitHub Actions workflow to completion.
If releasing openwork-orchestrator sidecars, build deterministically with SOURCE_DATE_EPOCH, upload assets to openwork-orchestrator-vX.Y.Z, and publish openwork-orchestrator.
If openwork-server or opencode-router versions changed, publish those packages.

Report what you changed, the tag created, and the GHA status.

1.0 KiB Raw Blame History

1.0 KiB

Raw Blame History