andesine 0.4.0 → 0.6.0

package/CHANGELOG.md

@@ -1,5 +1,41 @@
 # Changelog
 
+## 0.6.0
+
+- Validate extension manifests with the 0.6.0 rules: `settingsSections` is no longer
+  accepted, and element views accept a `description` and an `icon`, whose CSS
+  `extensions build` generates with the other manifest icons.
+- Update the `extensions init` template: block action samples without UI (“Shout”), with a
+  `Menu` (“Count words”), and with a `Dialog` (“Wrap in Note”); a “More” menu and an “About”
+  dialog in the panel sample; a description and an icon for the Note view; and a local setup
+  guide in its README. The bookmarks panel and the About settings section samples, and the
+  declared request URL, are removed.
+- Simplify the buttons of the `pages init` template: one `variant` (`primary`, `secondary`, or
+  `ghost`) replaces `variant` and `color`, and buttons default to the small size.
+
+## 0.5.0
+
+- Accept the `extensions` role permission (manage workspace extensions) in role commands.
+- Add `andesine extensions init [directory]`, which creates an extension with a backend
+  from the template of the same release and generates its first backend key.
+- Add `andesine extensions build`: manifest validation with the registry rules, the
+  frontend bundle with the generated `startExtension` call, view and icon CSS, and
+  `dist/extension.json` with the artifact digests and sizes.
+- Add `andesine extensions keys generate`, `check`, and `revoke`. Private keys stay in
+  `.andesine/keys` and are never uploaded.
+- Leave extension-only API operations (which need extension JWTs) out of the generated
+  command bindings.
+- Add `andesine extensions dev`, which runs an extension on a local instance for the
+  signed-in member: it uploads each build with a development key, reloads it on changes,
+  writes the key and the instance URL to the backend's `.env`, and stops it on exit
+  (`--remove` uninstalls it; `--backend <url>` points it at a local backend). It refuses hosts
+  that are not local.
+- Add `andesine extensions test-event <webhook> <type>` for sample events to the
+  development extension's webhooks.
+- Add `andesine extensions registry check` and `registry build` for extension registry CI:
+  validation with the instance rules, new versions without overwriting published ones, and
+  the registry index.
+
 ## 0.4.0
 
 - Add `andesine pages init [directory]`, which creates an Andesine Pages site from

package/README.md

@@ -32,6 +32,72 @@ template of this CLI release, with `@andesine/pages` and `@andesine/ui` pinned t
 same version. Then run `npm install` and `npm run dev` in the directory. The command
 needs no credentials.
 
+## Extensions
+
+```sh
+npx andesine extensions init hello --name acme/hello
+npx andesine extensions build
+npx andesine extensions keys generate
+npx andesine extensions keys check --registry https://registry.example.com/index.json
+npx andesine extensions keys revoke key-2026-10-07
+```
+
+`extensions init` creates an extension with a Solid frontend and a Node backend in a new or
+empty directory (default `extension`), and generates its first backend key.
+
+`extensions build` loads `andesine.config.ts`, validates the manifest with the same rules
+as the extension registry, bundles the frontend into one script with a generated
+`startExtension` call for the manifest's view entries, and generates the CSS of the views
+and of the manifest icons. It writes `dist/frontend.js`, `dist/styles.css`,
+`dist/icons.css`, and `dist/extension.json` (the manifest and the SHA-256 digest and size
+of each file). Builds are deterministic.
+
+`extensions keys generate` creates an Ed25519 key pair. The public key goes to
+`andesine.keys.json`, which the manifest imports; the private key goes to
+`.andesine/keys/<kid>.json` (mode 0600) and is never uploaded. `keys check` compares the
+private key in `ANDESINE_EXTENSION_KEY` or `--key` with the manifest keys and, with
+`--registry`, with the keys of the registry entry. `keys revoke` moves a key ID to
+`revokedKeys`. Extension commands use `--root <directory>` (default: current directory);
+only `dev` and `test-event` need credentials.
+
+### Local development
+
+```sh
+npx andesine --base-url http://localhost:3333 --workspace ws_... extensions dev
+npx andesine extensions test-event content entry.created
+npx andesine extensions dev --remove
+```
+
+`extensions dev` runs the extension on a local instance for the signed-in member only. It
+needs `andesine auth login` against that instance (API keys cannot develop extensions), a
+selected workspace, and `EXTENSIONS_DEVELOPMENT_ENABLED=true` on the local backend; it refuses
+other hosts than `localhost`, `127.0.0.1`, `[::1]`, `*.localhost`, `*.local`, and `*.test`.
+It creates a development key pair in `.andesine/keys/development.json`, uploads only its
+public key with each build, and writes the private key and the instance URL to the backend's
+environment file (`--env-file`, default `.env`). `--backend <url>` uses a local backend URL
+in place of the manifest's, so the manifest can keep its HTTPS deployment URL. Each change rebuilds and reloads the
+extension; a failed build waits for the next change. A build that asks for more permissions
+waits for approval in Settings → Extensions. Ctrl+C stops the extension and keeps its
+configuration and storage. `extensions test-event <webhook> <type>` sends a sample event to a
+webhook and reports the first attempt; `extensions dev --remove` uninstalls the development
+extension and deletes its state.
+
+### Registry
+
+```sh
+npx andesine extensions registry check --published <site checkout>
+npx andesine extensions registry build --published <site checkout> --site-url https://extensions.andesine.app
+```
+
+For the CI of an extension registry repository (projects under `extensions/<scope>/<name>`,
+each with `andesine.registry.json` for the publisher, and `registry/revocations.json`).
+`registry check` validates every project with the instance rules: manifests, keys (published
+keys never change, revoked keys stay revoked), version order, published versions that cannot
+change and must rebuild to the same styles, revocations, and no removed extensions.
+`registry build` runs the check, writes each new version's files and `version.json` next to the
+published ones without overwriting them, and writes `index.json` last. Dependencies of each
+project must be installed.
+
 ## Project configuration
 
 Run `andesine init` for guided setup. It uses Clack prompts and progress indicators