@nearform/fling 0.5.1 → 0.6.0

package/CHANGELOG.md

@@ -1,6 +1,35 @@
 # Changelog
 
-## Unreleased
+## 0.6.0
+
+- `fling groups --members a,b` lists only the groups whose members are exactly those people, to
+  find a group to use before making another. The MCP tool `fling_groups` takes `members` for the
+  same.
+
+- **Shared with me.** `fling ls --shared` lists the restricted sites other people have shared with
+  you, by address or through a group you are in, with their owner and how (`--sort` as for
+  `fling ls`; `--json`: `{ name, url, reviewUrl?, owner, via: { direct, groups }, createdAt,
+  updatedAt }`). The MCP tool `fling_list` takes `shared: true` for the same list, on a Fling with
+  the `audiences` capability.
+
+- **Groups.** `fling groups` lists the groups of people on a Fling (`--mine`: yours), and `show`,
+  `create`, `add`, `remove`, `rename` and `delete` manage them. Anyone can see a group and use it;
+  only its owner can change it. `fling access <name> --group <slugs>` / `--remove-group` put groups
+  in a site's audience. The MCP tools `fling_groups`, `fling_group_show`, `fling_group_create`,
+  `fling_group_members`, `fling_group_rename` and `fling_group_delete` do the same on a Fling with
+  the `groups` capability, and `fling_set_audience` takes `addGroups`, `removeGroups` and
+  `setGroups`. A site's `audience.groups` is `[{ slug, name, size }]`, and sites carry
+  `audienceGroups`.
+- `fling access <name>` shows who can open a private site and, with `--add`, `--remove` or
+  `--clear`, limits it to listed people (its audience) or opens it to everyone signed in again.
+  It warns while a share link still opens a restricted site, and when the site is public (the
+  audience applies once it is private). `fling info` shows the same line.
+- The MCP tool `fling_set_audience` (`add`, `remove`, `set`, `clear`) does the same, on a Fling
+  that has the `audiences` capability, and `fling_info` says who can open the site.
+- Sites in `--json` output carry `restricted` (private with an audience) and `audienceSize`;
+  `fling info --json` adds the `audience` itself.
+- `fling ls` lists the last updated site first. `--sort updated|created|name` picks the order
+  (`created`: newest first; `name`: A–Z). The MCP tool `fling_list` takes the same `sort`.
 
 ## 0.5.1
 

package/README.md

@@ -178,15 +178,69 @@ and a taken name fails (exit 1) with suggestions rather than picking another nam
 
 | Command | |
 |---|---|
-| `fling ls [--archived]` | your sites |
+| `fling ls [--archived] [--sort updated\|created\|name]` | your sites, last updated first (`created`: newest first; `name`: A–Z) |
+| `fling ls --shared [--sort …]` | the restricted sites others have shared with you: owner, and how (your address or a group) |
 | `fling info <name>` / `fling versions <name>` | details and version history |
 | `fling files <name> [versionId]` | the files in the live version (or an earlier one) |
 | `fling rollback <name> <versionId>` | serve an earlier version |
 | `fling share <name> [--refresh] [--revoke]` | public share link: print or create it, rotate it, or remove it |
 | `fling visibility <name> private\|public` | require sign-in, or not |
+| `fling access <name> [--add <emails>] [--remove <emails>] [--group <slugs>] [--remove-group <slugs>] [--clear]` | who can open a private site: everyone signed in, or only listed people and groups |
 | `fling archive <name>` / `fling unarchive <name>` | take offline and keep the files, or bring back |
 | `fling rm <name> [--yes]` | delete permanently |
 
+### Who can open a private site
+
+A private site opens to everyone signed in to your Fling. `fling access` limits it to listed people
+(its audience); you, the owner, can always open it:
+
+```sh
+fling access my-app                                   # who can open it now
+fling access my-app --add bob@example.com,cat@example.com
+fling access my-app --remove bob@example.com
+fling access my-app --group design                    # everyone in the design group too
+fling access my-app --remove-group design
+fling access my-app --clear                           # everyone signed in again
+```
+
+Addresses are comma-separated or given after `--add` one by one, and each must be one that can sign
+in to the Fling. Someone who hasn't signed in yet is marked `(hasn't signed in yet)`; they can open
+the site once they do. The audience only applies while the site is private: on a public site it is
+kept for later and `fling access` says so. A share link still opens a restricted site to anyone who
+has it, and `fling access` warns while one exists. Removing someone shuts them out within 5
+minutes. `--json` prints the site with its `audience` (`{ emails: [{ email, known }], groups:
+[{ slug, name, size }] }`) and `warnings`; `fling info` shows the same line, and `fling ls --json`
+gives each site's `restricted`, `audienceSize` and `audienceGroups` (how many of those are groups).
+
+`fling ls --shared` lists the other side: the restricted sites whose audience names you, or a group
+you are in, with their owner and how they reached you. With `--json`, each is `{ name, url,
+reviewUrl?, owner, via: { direct, groups }, createdAt, updatedAt }`. Your own sites, and private
+sites open to everyone signed in, aren't listed.
+
+### Groups
+
+A group is a named list of people, such as a team, that anyone signed in can use in a site's
+audience. Everyone can list groups and see who is in one; only the group's owner, who made it, can
+change its members, rename it or delete it:
+
+```sh
+fling groups                                          # every group (--mine: only yours)
+fling groups --members bob@example.com,cat@example.com  # the groups of exactly these people
+fling groups show design                              # its members
+fling groups create design --name "Design team" --add bob@example.com,cat@example.com
+fling groups add design dan@example.com
+fling groups remove design bob@example.com
+fling groups rename design "Designers"
+fling groups delete design                            # asks first unless --yes
+```
+
+A slug is lowercase letters, digits and single hyphens, unique on the Fling; a group holds up to 500
+people, and an audience names up to 10 groups. Taking someone out of a group shuts them out of the
+sites it opens within 5 minutes. Deleting a group never opens a site up: sites whose audience
+names it keep their restriction, and anyone it let in loses access. Where it was the only entry,
+`fling access` shows "a deleted group (#<id>)" and only you can open the site until you add
+people or groups (`--remove-group '#<id>'` takes the reference out).
+
 ## Comments
 
 People review a site on its review page (`<your Fling>/review/<name>`, the **Review** button on the
@@ -261,7 +315,11 @@ The MCP tools:
   current), read when called. `{use: <server>}` makes one current, the same as `fling use`.
 - `fling_check_name`, `fling_list`, `fling_info`, `fling_files`, `fling_share`,
   `fling_set_visibility`, `fling_archive`, `fling_rollback`, `fling_delete` (needs
-  `confirm: true`), `fling_whoami`, and the comment tools when a Fling has comments.
+  `confirm: true`), `fling_whoami`, the comment tools when a Fling has comments, and
+  `fling_set_audience` (`add`, `remove`, `set` or `clear` the people who can open a private site,
+  and `addGroups`, `removeGroups`, `setGroups` for groups) when it can limit sites to listed
+  people, and the group tools (`fling_groups`, `fling_group_show`, `fling_group_create`,
+  `fling_group_members`, `fling_group_rename`, `fling_group_delete`) when it has groups.
 
 Results that give URLs (deploys, publishes, comments) end with the Fling they went to.