@pmate/cli 0.41.1 → 0.42.1

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
@@ -363,6 +363,32 @@ Android services use `pmate service deploy pmate:merry-android`. The primary ser
363
363
 
364
364
  Use --variant, --bump, --force, --release-notes or --minimum-version-code to override release options. --dry-run prints the plan without incrementing versions, resolving signing secrets, building or uploading. Android currently does not support --local/--unsigned. service apk release was removed; service apk list remains a query.
365
365
 
366
- HarmonyOS NEXT projects exist in parrot-native (apps/pmate-app-harmony and apps/time-duck-harmony). They currently use signed build scripts and a GitHub Actions workflow, not a registered PMate service type or automatic AppGallery submission.
366
+ HarmonyOS NEXT projects exist in parrot-native (apps/pmate-app-harmony and apps/time-duck-harmony). They have signed build scripts and a GitHub Actions workflow; CLI 0.42.0+ also supports a harmonyos service through service deploy. AppGallery submission is separate.
367
367
 
368
368
  Android production releases check the existing current and compatibility update manifests before changing source versions or loading signing secrets. A candidate versionCode must exceed every published versionCode; stale checkouts are rejected and must be updated explicitly. APK package identity must match the registered service before upload.
369
+
370
+ ### HarmonyOS distribution
371
+
372
+ `pmate service deploy pmate:merry-harmony` dispatches a harmonyos service. mobile holds bundleName, repository and dir; build.script defaults to scripts/build-release.sh. The service must associate exactly one app ID. The source AppScope/app.json5 controls the published version. Only prod is supported. --dry-run inspects the plan without SDK or secrets; --local builds verified signed artifacts without upload; --out-dir overrides the local output base. Other platforms' flags are rejected.
373
+
374
+ Install the DevEco SDK, ohpm, Hvigor and Java. Configure DEVECO_SDK_HOME, OHPM_BIN, HVIGORW_BIN, optionally NODE_BIN, JAVA_BIN and HAP_SIGN_TOOL for non-default installations. Service prod Secrets are HARMONY_KEYSTORE_BASE64, HARMONY_CERTIFICATE_BASE64, HARMONY_PROFILE_BASE64, HARMONY_STORE_PASSWORD, HARMONY_KEY_ALIAS and HARMONY_KEY_PASSWORD. Local signing variables are not used. Missing tools or credentials stop the real build.
375
+
376
+ 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
+
378
+ 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.
379
+
380
+ ## Bot profile nicknames
381
+
382
+ ### Background
383
+
384
+ 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:
385
+
386
+ ```bash
387
+ pmate account bot profile update --app pmate:merry --name blackbeard --nickname "黑胡子BOT" --json
388
+ # Equivalent shortcut:
389
+ pmate account bot nickname --app pmate:merry --name blackbeard --nickname "黑胡子BOT" --json
390
+ ```
391
+
392
+ `--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.
393
+
394
+ 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";