@pmate/cli 0.39.0 → 0.40.0

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
@@ -270,10 +270,10 @@ Meili's Host may pass `--actor-profile-id` with `PMATE_LOG_DELEGATE_TOKEN` in th
270
270
 
271
271
  Packaged installers are automatically uploaded to Aliyun OSS (`parrot-static`), using the same credentials as Android APK releases. The completion output and build report include public download URLs, SHA-256 checksums, and a `release.json` URL. Configure `oss.public.region` and `aliyun.ak/sk` in your PMate configuration. Conflicting published versions require an app version bump. `--dir` produces local unpacked output only; `--dry-run` does not upload. The CLI owns publication after electron-builder completes; electron-builder receives the immutable generic release URL only to generate valid package metadata and runs with publishing disabled.
272
272
 
273
- `pmate app build <ns:app>` packages a native shell that loads its configured HTTPS origin directly, without building or embedding web resources, and produces macOS DMG/ZIP or Windows NSIS/ZIP artifacts. Packaged releases require a CLI login with admin permission in the app namespace; `--unsigned`, `--dir` and `--dry-run` stay local. Signed builds are the default; `--signed` remains accepted. Config is discovered from the current directory towards the repository root, checking desktop.config.json and apps/<app-name>/desktop.config.json at each level. Ambiguous matches require --config. Platform and architecture default to the host and Node architecture; output defaults to release/<app-name> at the repository root (or config directory outside a repository). Optional config notaryProfile selects a local Keychain profile; APPLE_KEYCHAIN_PROFILE overrides it. macOS publication requires Developer ID signing, notarization and Gatekeeper acceptance. The first build downloads pinned Electron and electron-builder versions. Current targets: macOS and Windows, `arm64` and `x64`; macOS packages require a macOS build host.
273
+ `pmate service deploy <ns:electron-service>` packages a native shell that loads its configured HTTPS origin directly, without building or embedding web resources, and produces macOS DMG/ZIP or Windows NSIS/ZIP artifacts. Packaged releases require a CLI login with admin permission in the app namespace; `--dry-run` only prints a plan; `--local` keeps build artifacts local, and is required with `--unsigned` or `--dir`. Signed builds are the default; `--signed` remains accepted. The service type must be electron, repository/dir locate the source, appIds must contain exactly one application identity, and optional build settings include config (relative to service dir, default desktop.config.json), platform and arch. The desktop config app must match the associated application, not the service ID. Platform and architecture default to the host and Node architecture; output defaults to release/<service-name> at the repository root. Optional desktop config notaryProfile selects a local Keychain profile; APPLE_KEYCHAIN_PROFILE overrides it. macOS publication requires Developer ID signing, notarization and Gatekeeper acceptance. The first build downloads pinned Electron and electron-builder versions. Current targets: macOS and Windows, `arm64` and `x64`; macOS packages require a macOS build host.
274
274
 
275
275
  ```sh
276
- pmate app build pmate:hello --target electron --config apps/hello/desktop.config.json --platform mac --arch arm64 --out-dir release/desktop
276
+ pmate service deploy pmate:merry-electron
277
277
  ```
278
278
 
279
279
  Config schema 2 (`icon` is relative to the config file; migrate schema 1 by removing `web` and changing `schemaVersion` to 2):
@@ -329,12 +329,12 @@ On macOS with Xcode, a signed-in Apple developer account, valid signing profiles
329
329
 
330
330
  ```sh
331
331
  # First build on this machine: import the highest Build already used in Apple.
332
- pmate service ios build td:time-duck-ios --scheme TimeDuck --team D9D59BE76S --last-build 2026101501
332
+ pmate service deploy td:time-duck-ios --last-build 2026101501
333
333
  # Subsequent builds on this machine:
334
- pmate service ios build td:time-duck-ios --scheme TimeDuck --team D9D59BE76S
334
+ pmate service deploy td:time-duck-ios
335
335
  ```
336
336
 
337
- `service ios build` archives Release and uploads directly to App Store Connect for TestFlight. It preserves the marketing version (for example `0.1.0`) and increments only the integer Build by one. It does not publish an App Store release. `uploaded-processing` means Apple accepted the upload; processing and TestFlight download availability require separate verification.
337
+ `service deploy` for a service with type ios archives Release and uploads directly to App Store Connect for TestFlight. It preserves the marketing version (for example `0.1.0`) and increments only the integer Build by one. It does not publish an App Store release. `uploaded-processing` means Apple accepted the upload; processing and TestFlight download availability require separate verification.
338
338
 
339
339
  Register an `ios` service with `repository` and `dir`. `--cwd` overrides the repository root; `--project` / `--workspace` paths are relative to the app directory. Exactly one discovered project/workspace is required unless explicitly selected. Always provide `--scheme`; `--team` overrides the project's signing team. `--json` returns version, Build, archive and log paths after upload.
340
340
 
@@ -343,3 +343,16 @@ The first invocation for each marketing version requires `--last-build <highest-
343
343
  Sequences, retained archives, derived data and logs live in `~/.pmate/ios-builds/`. Project/source version files are not changed. A bundle-level exclusive lock prevents simultaneous builds on the same machine; it does not coordinate different machines. Build/upload failures keep the reserved number and logs; retry consumes the next number. After an interrupted process, remove a leftover `.lock` file only after confirming no build is still running. Builds require automatic signing; resolve Apple account/certificate/profile errors in Xcode. Extension or App targets with fixed plist versions must produce matching archive metadata or the upload is stopped.
344
344
 
345
345
  `pmate service deploy <ns:service>` defaults to `--env prod` for every service. Use explicit `--env preview` or `--env dev` to override it. For example, `pmate service deploy pmate:merry` deploys the production site https://merry.pmate.chat.
346
+
347
+ ### Unified native service deployment
348
+
349
+ Web, iOS and Electron use separate services. Deploy dispatches by registered type, without --target. For iOS store scheme/team and optional project/workspace under build; existing mobile bundle identity stays unchanged. Native deployment currently supports prod only. Override registered settings with --cwd, --scheme, --team, --project, --workspace or Electron-specific --config, --platform, --arch and --out-dir. Unsupported options fail explicitly. iOS --dry-run resolves the registered plan without running Xcode or uploading.
350
+
351
+ ```sh
352
+ pmate service deploy pmate:merry
353
+ pmate service deploy pmate:merry-ios
354
+ pmate service deploy pmate:merry-electron
355
+ pmate service deploy pmate:merry-electron --local --unsigned
356
+ ```
357
+
358
+ app build and service ios build were removed; use service deploy. Local and dry-run runs do not create successful deploy-history entries. iOS upload success is recorded as uploaded-processing, not TestFlight availability.
package/dist/index.d.ts CHANGED
@@ -816,19 +816,6 @@ type StoreCommandArgs = ({
816
816
  filePath?: string;
817
817
  } & StoreSharedArgs);
818
818
  type AppCommandArgs = {
819
- type: Command.App;
820
- action: "build";
821
- id: string;
822
- target: "electron";
823
- config?: string;
824
- platform: string;
825
- arch: string;
826
- outDir?: string;
827
- dryRun: boolean;
828
- signed: boolean;
829
- dir: boolean;
830
- json: boolean;
831
- } | {
832
819
  type: Command.App;
833
820
  action: "list";
834
821
  namespace?: string;
@@ -953,6 +940,20 @@ type ServiceCommandArgs = {
953
940
  } | {
954
941
  type: Command.Service;
955
942
  action: "deploy" | "stop";
943
+ dryRun?: boolean;
944
+ local?: boolean;
945
+ unsigned?: boolean;
946
+ signed?: boolean;
947
+ dir?: boolean;
948
+ config?: string;
949
+ platform?: string;
950
+ arch?: string;
951
+ outDir?: string;
952
+ scheme?: string;
953
+ team?: string;
954
+ project?: string;
955
+ workspace?: string;
956
+ lastBuild?: number;
956
957
  namespace: string;
957
958
  name: string;
958
959
  env?: string;
@@ -1003,19 +1004,6 @@ type ServiceCommandArgs = {
1003
1004
  dryRun: boolean;
1004
1005
  baseUrl?: string;
1005
1006
  json: boolean;
1006
- } | {
1007
- type: Command.Service;
1008
- action: "ios-build";
1009
- namespace: string;
1010
- name: string;
1011
- scheme: string;
1012
- project?: string;
1013
- workspace?: string;
1014
- team?: string;
1015
- cwd?: string;
1016
- lastBuild?: number;
1017
- baseUrl?: string;
1018
- json: boolean;
1019
1007
  } | {
1020
1008
  type: Command.Service;
1021
1009
  action: "apk-release";