@greenblacksky/honmoon 0.4.0 → 0.4.1

package/README.md

@@ -53,15 +53,19 @@ every running app reloads with the change.
 
 The version number still matters. Each app asks for a range
 (`"@greenblacksky/honmoon": "^0.4.0"`), and the workspace only links this folder
-when its version fits. For a change the apps must adapt to, bump it
-(`npm version minor`), update the range in each app, and once the repos
-are on GitHub tag the commit, so you can always tell which engine an app
-was tested with.
-
-Building an app outside the workspace (for example, automatic
-builds on GitHub) needs Honmoon published to a package registry. How to do
-that (publicly on npmjs.com, or privately on GitHub Packages), and the GitHub Actions pipeline for
-the apps, is in [docs/PUBLISHING.md](docs/PUBLISHING.md).
+when its version fits. For a change the apps must adapt to, bump the minor
+version and update the range in each app.
+
+Outside the workspace (for example, an app built on GitHub) the apps
+install the published package from npmjs.com instead. A release takes two
+commands in this folder:
+
+```
+npm version patch      0.4.0 → 0.4.1 (minor for 0.5.0): commits and tags v0.4.1
+git push --follow-tags GitHub sees the tag, checks, tests and publishes
+```
+
+How it was set up is in [docs/PUBLISHING.md](docs/PUBLISHING.md).
 
 ## Tests
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@greenblacksky/honmoon",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Honmoon: the engine under Mira, Rumi and Zoey — the music model, spaced repetition, audio, notation drawing and the shared Svelte screens.",
   "license": "MIT",
   "repository": {