@pmate/cli 0.42.0 → 0.42.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -4,7 +4,9 @@ A TypeScript-powered command-line tool scaffold for future pMate automation.
4
4
 
5
5
  ## Deploy from an isolated checkout
6
6
 
7
- Local-build services can be released without modifying the conventional `~/dev/pmate` checkout. Use `pmate service deploy pmate:<service> --env prod --cwd /absolute/path/to/repo` for Vite, static or FC services. The registered service directory is resolved relative to that repository root; `--cwd` does not change the service's registered repository or environment.
7
+ Vite deployments reject `--cwd`. They use the registered repository's conventional local checkout (`~/dev/pmate/<repository>`), refuse any uncommitted changes (including untracked files), fetch the latest GitHub `main`, switch to `main` and fast-forward to that exact revision. A missing remote `main`, failed switch/fetch, or local main with unpushed/divergent commits aborts before dependency installation, build or upload. No changes are stashed, reset or discarded. Dependencies are installed with `pnpm install --frozen-lockfile`; the deployed commit SHA is printed. Commit and push changes to `main` before deploying.
8
+
9
+ Static and FC services can be released without modifying the conventional `~/dev/pmate` checkout. Use `pmate service deploy pmate:<service> --env prod --cwd /absolute/path/to/repo` for static or FC services. The registered service directory is resolved relative to that repository root; `--cwd` does not change the service's registered repository or environment.
8
10
 
9
11
  Remote Node/Python/Rust deployments still use the registered repository and reject `--cwd` instead of silently ignoring it. Merge and push the intended release to `main` before deployment. The normal service deploy-history and log flow is unchanged.
10
12
 
@@ -376,3 +378,19 @@ Install the DevEco SDK, ohpm, Hvigor and Java. Configure DEVECO_SDK_HOME, OHPM_B
376
378
  Builds run in private temporary source/SDK copies. The CLI verifies APP, HAP and embedded module signatures, signer certificate and compiled identity/version, then uploads both files and immutable release.json under harmony/<namespace>/<service>/<versionName>/<versionCode>/ in parrot-static, followed by latest.json. Existing or older versions are rejected. Native service history records the manifest URL. Signing keys and temporary sources are cleaned; logs and verified local outputs remain under ~/.pmate/harmony-builds/ by default. Publication means OSS distribution, not AppGallery submission, approval or device installation.
377
379
 
378
380
  HarmonyOS publication uses an ownership-checked service lock in an unversioned OSS bucket and forbid-overwrite for immutable files. It checks the latest version again under the lock. Interrupted publishers may leave a lock; confirm they have stopped before clearing it. The CLI does not automatically steal stale locks.
381
+
382
+ ## Bot profile nicknames
383
+
384
+ ### Background
385
+
386
+ Chat displays a bot profile's `nickName`. To change that display name without changing the bot's internal name, account, credentials, or agent configuration, update the existing profile:
387
+
388
+ ```bash
389
+ pmate account bot profile update --app pmate:merry --name blackbeard --nickname "黑胡子BOT" --json
390
+ # Equivalent shortcut:
391
+ pmate account bot nickname --app pmate:merry --name blackbeard --nickname "黑胡子BOT" --json
392
+ ```
393
+
394
+ `--name` is the bot's internal name, as returned by `pmate account bot list --app pmate:merry --json`. Both commands require an existing CLI login, use the active session, and rely on the auth API's profile update permissions. They require exactly one profile for the bot account in the specified app; missing or multiple profiles cause an error without a write. These commands never create a profile.
395
+
396
+ The CLI updates only `nickName` through `PUT /profile`, then polls the profile index for up to approximately 10 seconds and returns the verified profile. A matching nickname is a no-op. If verification times out, the update may already have been applied; inspect the profile before retrying. `--base-url` selects the auth API for all requests.
package/dist/index.d.ts CHANGED
@@ -471,6 +471,14 @@ type AccountCommandArgs = {
471
471
  role?: "practitioner" | "mate";
472
472
  baseUrl?: string;
473
473
  json: boolean;
474
+ } | {
475
+ type: Command.Account;
476
+ action: "bot-profile-update";
477
+ app: string;
478
+ name: string;
479
+ nickName: string;
480
+ baseUrl?: string;
481
+ json: boolean;
474
482
  } | {
475
483
  type: Command.Account;
476
484
  action: "access-key-create";