Workspace commands (hws)latest · 0.1.2

`hws promote`

Move a published version to a later channel.

hws promote <CODE>@<version> --to beta|stable
            [--from dev|beta] [--org <slug>] [--notes <text>] [--json]

Also available as horizech hws promote.

Promotion reuses the file already in the registry; nothing is rebuilt or uploaded. Versions only move forward: dev → beta, dev → stable or beta → stable. See Channels.

Without --from, the CLI uses the nearest earlier channel that has the version: beta before dev when promoting to stable.

Arguments

Argument	Description	Default
`<CODE>@<version>`required	The package code and the exact version, e.g. `[email protected]`. `latest` is not accepted here.

Options

Option	Description	Default
`--to <channel>`required	`beta` or `stable`.
`--from <channel>`	`dev` or `beta`.	found automatically
`--org <slug>`	The organization that owns the package.	found from the package code
`--notes <text>`	A note stored with the promotion.
`--json`	Print a machine-readable result on stdout. Progress goes to stderr.

Examples

Release a tested version

$ hws promote [email protected] --to stable

Promote from beta explicitly

$ hws promote [email protected] --from beta --to stable

With `--json`

stdout

{
  "org": "acme",
  "code": "HWS_APP_NOTES",
  "version": "1.4.0",
  "from": "dev",
  "to": "stable",
  "result": { "Version": "1.4.0", "SourceChannel": "dev", "TargetChannel": "stable" }
}

API calls

What this command calls, for debugging and for anyone scripting the same thing. Registry paths are on https://api.horizech.com, OAuth2 paths on https://horizech.com. See Registry API.

Method	Path	Notes
`GET`	`/api/v1/packages/:org/:code/versions/:version/manifest?channel=…`	finding --from
`POST`	`/api/v1/packages/:org/:code/promote`	JSON: Version, SourceChannel, TargetChannel, Notes

hws promote