matterbridge-dynalite 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,6 +1,10 @@
 # Changelog
 
-## 0.1.0 — unreleased
+## 0.1.1 — 2026-10-15
+
+- The first release published from GitHub, through npm's trusted publishing; the code is as in 0.1.0.
+
+## 0.1.0 — 2026-10-14
 
 First version.
 

package/README.md

@@ -140,7 +140,9 @@ To try a local build in Matterbridge, run `matterbridge -add /path/to/matterbrid
 1. Set the new version in `package.json` (and in `CHANGELOG.md`), and push it.
 2. Make a GitHub release with the tag `v<version>`, e.g. `v0.1.0`.
 
-The *Publish* workflow then tests it and publishes it to npm with provenance, through npm's trusted publishing (no token in the repository). A release marked as a pre-release goes out under the `next` tag, so Matterbridge keeps offering the last full release.
+3. Approve it on npmjs.com (*Staged Packages*, with 2FA) or with `npm stage approve <id>`.
+
+The *Publish* workflow tests it and stages it on npm through trusted publishing (no token in the repository); nothing goes live until a maintainer approves it. A release marked as a pre-release goes out under the `next` tag, so Matterbridge keeps offering the last full release.
 
 ## Licence
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "matterbridge-dynalite",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Signify Dynalite",
   "author": "https://github.com/jonaskul",
   "license": "Apache-2.0",