meshbay.git/packages/meshbay-hub/src/meshbay_hub/__init__.py, branch 0.2MeshBay — read-only public mirrorhttps://git.meshbay.org/meshbay.git/atom?h=0.22026-08-14T18:54:47Zchore: release 0.2.02026-08-14T18:54:47ZChristophe Bessoncbesson@gmail.com2026-08-14T18:54:47Zurn:sha1:e525f7e123b621deec10a9719efa10ccafa93ad0
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>
chore: initialize monorepo structure for MeshBay2026-08-09T01:52:58ZChristophe Bessoncbesson@gmail.com2026-08-09T01:52:58Zurn:sha1:271adc8504aad32075d75d06fd42023877a649ec
3-package layout: meshbay-common (shared crypto/protocol),
meshbay-hub (FastAPI server), meshbay-node (local daemon).
Includes validated POC spikes 1-6 in poc/, architecture drafts
v1/v2 in docs/, and CLAUDE.md project conventions.
All cryptographic primitives extracted from POC into
meshbay_common/crypto.py (GEK wrap/unwrap, chunk key derivation,
keystore encryption, chunk signing).
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>