@homespunapps/cli 1.6.17 → 1.6.19

package/dist/commands/members.js

@@ -104,29 +104,42 @@ async function runSetRole(args) {
     assertKnownFlags(args, ...specFor("members", "set-role"));
     const appArg = args.flags.get("app");
     if (!appArg) {
-        fail("usage: homespun members set-role --app <idOrSlug> --human <humanId> (--custom-role <name> | --clear-role)", "invalid_args");
+        fail("usage: homespun members set-role --app <idOrSlug> --human <humanId> (--custom-role <name[,name...]> | --clear-role)", "invalid_args");
     }
     const humanId = args.flags.get("human");
     if (!humanId) {
         fail("--human is required", "invalid_args");
     }
-    // Clearing a role is a real instruction, so it gets its own explicit flag
-    // rather than being spelled as an omitted or empty --custom-role: an omitted
-    // value must never silently wipe someone's role.
+    // Clearing a member's roles is a real instruction, so it gets its own
+    // explicit flag rather than being spelled as an omitted or empty
+    // --custom-role: an omitted value must never silently wipe someone's roles.
     const customRole = args.flags.get("custom-role");
     const clear = args.bools.has("clear-role");
     if (clear && customRole !== undefined) {
         fail("--custom-role and --clear-role are mutually exclusive", "invalid_args");
     }
     if (!clear && customRole === undefined) {
-        fail("one of --custom-role <name> or --clear-role is required", "invalid_args");
-    }
+        fail("one of --custom-role <name[,name...]> or --clear-role is required", "invalid_args");
+    }
+    // A member may hold several roles, so the flag takes a comma-separated list.
+    // A role name can never contain a comma (the manifest validator's role-name
+    // grammar is lowercase letters, digits and underscore), so the split is
+    // unambiguous. An empty entry is rejected rather than dropped: a trailing
+    // comma is a typo, and silently ignoring it would apply a role set the caller
+    // did not write.
+    const customRoles = clear
+        ? []
+        : customRole.split(",").map((r) => {
+            const trimmed = r.trim();
+            if (trimmed.length === 0) {
+                fail("--custom-role must not contain an empty role name", "invalid_args");
+            }
+            return trimmed;
+        });
     const client = makeClient(args);
     const appId = await resolveAppId(client, appArg);
     try {
-        printJson(await client.setAppMemberRole(appId, humanId, {
-            customRole: clear ? null : customRole,
-        }));
+        printJson(await client.setAppMemberRole(appId, humanId, { customRoles }));
     }
     catch (e) {
         failFromError(e);

package/dist/help-catalog.js

@@ -338,7 +338,7 @@ const MEMBERS = {
         },
         {
             verb: "set-role",
-            summary: "Changes an existing member's custom role in place.",
+            summary: "Replaces an existing member's declared roles in place.",
             flags: [
                 {
                     name: "app",
@@ -352,8 +352,8 @@ const MEMBERS = {
                 },
                 {
                     name: "custom-role",
-                    value: "<name>",
-                    description: "Custom role to assign; must be declared in the app's manifest",
+                    value: "<name[,name...]>",
+                    description: "Declared role(s) to assign, comma-separated; each must be declared in the app's manifest",
                 },
             ],
             bools: [
@@ -808,7 +808,7 @@ const DEPLOY = {
     notes: [
         "Packaging has one canonical shape and one escape hatch. A directory deploy (homespun deploy ./my-app) reads ./my-app/index.html and ./my-app/manifest.json: fixed filenames, no discovery heuristics, and both files are required. The single-file escape hatch (homespun deploy ./index.html --manifest ./manifest.json) takes the manifest from --manifest, which accepts a file path or inline JSON.",
         "Create versus redeploy is decided by the presence of --app, not by two verbs. With no --app this creates an app (POST /v1/apps); new apps default to private (owner plus invited members, sign-in gated), --slug is accepted with private or public visibility including the default, and an explicit --visibility link always gets a server-generated slug and rejects --slug. With --app <id> this redeploys (POST /v1/apps/:id/versions), where --slug and --visibility are rejected because the slug is immutable and visibility changes go through 'homespun apps update'.",
-        "--check is a dry run. It runs the full manifest and asset-shape validation, the redeploy compat gate (with --app), and the schedule-timezone advisory, then prints { ok, warnings, compat, breaks } without creating a version or mutating anything. An invalid manifest fails the same way a real deploy would, and a narrowing redeploy reports the compat break instead of applying it.",
+        "--check is a dry run. It runs the full manifest and asset-shape validation, the redeploy compat gate (with --app), and the schedule-timezone advisory, then prints { ok, warnings, compat, breaks } without creating a version or mutating anything. An invalid manifest fails the same way a real deploy would, and a redeploy the compat gate would refuse reports the break instead of applying it.",
     ],
     outputNote: 'Output is JSON: { app_id, slug, url, version, visibility, created, share_url, compat, breaks, warnings }. share_url is present only when creating a link-visibility app: it carries the app share token in its #k= fragment and is shown ONCE, it is not recoverable later, and it can be rotated with \'homespun apps share-link rotate <app>\'. warnings flags non-fatal issues, for example an app that declares schedules with no timezone set (reminders fire at 08:00 UTC until one is set). Errors go to stderr as {"error":{"code","message"}} with a non-zero exit.',
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homespunapps/cli",
-  "version": "1.6.17",
+  "version": "1.6.19",
   "description": "Command-line client for the Homespun relay: deploy a real multi-user web app from your agent, then keep reading and writing its data.",
   "license": "MIT",
   "type": "module",
@@ -36,7 +36,7 @@
     "test:unit": "vitest run"
   },
   "dependencies": {
-    "@homespunapps/core": "^1.6.17",
+    "@homespunapps/core": "^1.6.19",
     "qrcode-terminal": "^0.12.0"
   },
   "devDependencies": {