v2.7.0

What's Changed

• fix: deploy never ran on release + contributing guide by @FelipeKreulich in #394
• release: fix deploy trigger + contributing guide by @FelipeKreulich in #395
• feat: serve the site and the relay on one domain, and announce the hub by @FelipeKreulich in #397
• release: serve the site and the relay on one domain by @FelipeKreulich in #398
• fix: a Caddyfile change never reached the running Caddy by @FelipeKreulich in #400
• release: fix the Caddyfile deploy trap by @FelipeKreulich in #401
• feat: monitor the hub from outside, and alert by issue by @FelipeKreulich in #407
• release: hub monitoring by @FelipeKreulich in #408
• feat: publish how busy the hub is, as a range by @FelipeKreulich in #410
• release: publish how busy the hub is by @FelipeKreulich in #411
• feat: ship the client as a standalone binary too by @FelipeKreulich in #412
• release: standalone client binary by @FelipeKreulich in #413
• chore(deps): take the August bumps, hold figlet, and point Dependabot at dev by @FelipeKreulich in #415
• release: August dependency bumps by @FelipeKreulich in #416
• chore: release 2.7.0 by @FelipeKreulich in #417
• release: 2.7.0 by @FelipeKreulich in #418

Full Changelog: v2.6.0...v2.7.0

---

The binaries that were attached here have been removed.

They did not work. sodium-native's native addon was never embedded, so every binary kept an absolute path back to the machine that built it and died with Cannot find addon anywhere else. CI did not catch it because it ran the binary on the runner that built it, where that path still existed.

Fixed in v2.7.2, which ships the first binaries verified on a machine that did not build them. If you downloaded one from this release, replace it.

The npm package was never affected — npx ciphermesh@latest does not use these files.