@fugood/bricks-cli 2.26.0-beta.24 → 2.26.0-beta.25

package/README.md

@@ -240,9 +240,14 @@ bricks app trigger <app-id> <test-id> [--play|--stop] [--setup-at-launch] [-g ma
 bricks app control-page <app-id> -t <short-edit,canvas-control,device-control,device-control-create-only> [--token-name name] [--expires-in days] [-e KEY=VALUE] [--no-token] [--dry-run] [-j|--json]
 # The printed URL is <controller>/<page>.html?workspace_secret=…&application_id=…; set BRICKS_CONTROLLER_URL to override the controller origin.
 
-# Preview a release without publishing
+# Create a release (--dry-run checks it without publishing). A semver --version must be newer than every semver release in the cloud (see `bricks app versions <app-id> -j`); non-semver labels such as the default app name work as before.
 bricks app release <app-id> -c <config-path-or-json> [-n name] [--version version] [--changelogs text] [--dry-run] [-j|--json]
 
+# CTOR projects: a config-only push (update-app) is the normal last step after edits.
+bricks ctor push --auto-commit -y
+# Release (deploy-app) only when a new version is requested. The version (from --version, --auto-version or package.json) must be semver and newer than every cloud release; a duplicate or lower one is refused before anything changes. There is no bypass flag: restore an old release with `bricks app switch-version`.
+bricks ctor deploy --auto-commit --version <next-version> -y
+
 # List release versions, then switch the platform config to one (ID or name).
 # The local CTOR project is not changed. Unreleased changes are dropped: confirm, or pass -y.
 bricks app versions <app-id> [-j|--json]