summaryrefslogtreecommitdiffstats
path: root/packaging/README.md
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-08-14 20:54:47 +0200
committerChristophe Besson <cbesson@gmail.com>2026-08-14 20:54:47 +0200
commite525f7e123b621deec10a9719efa10ccafa93ad0 (patch)
tree66377f199b478f01d662fb19e0da8297167303f7 /packaging/README.md
parentc83a4f6ab0c8a83e8679e78427ae60dc29bb2c60 (diff)
downloadmeshbay-0.2.tar.gz
chore: release 0.2.00.2
All three packages together, as the conventions require, plus the RPM and DEB metadata and their changelogs. The tag said 0.2 while every package announced 0.1.0, which would have shipped an RPM claiming to be the reviewed build while containing a different protocol: the hub schema lost the user identity keys, tokens lost pk_user, and gek_bundle_store left the wire. Pre-1.0, a breaking change bumps MINOR. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'packaging/README.md')
-rw-r--r--packaging/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/packaging/README.md b/packaging/README.md
index 2e31b7f..1b92947 100644
--- a/packaging/README.md
+++ b/packaging/README.md
@@ -32,9 +32,9 @@ dpkg-deb --build packaging/deb/meshbay-hub
dpkg-deb --build packaging/deb/meshbay-node
# Install
-sudo dpkg -i python3-meshbay-common_0.1.0_all.deb
-sudo dpkg -i meshbay-hub_0.1.0_all.deb
-sudo dpkg -i meshbay-node_0.1.0_all.deb
+sudo dpkg -i python3-meshbay-common_0.2.0_all.deb
+sudo dpkg -i meshbay-hub_0.2.0_all.deb
+sudo dpkg -i meshbay-node_0.2.0_all.deb
```
## Install order