v2.6.0
What's Changed
- chore: sha256 da fórmula Homebrew (2.5.0) by @FelipeKreulich in #372
- feat: limites de produção e controles de operador by @FelipeKreulich in #374
- docs: template de termos de uso (EN + PT) by @FelipeKreulich in #376
- release: limites de produção, controles de operador e termos de uso by @FelipeKreulich in #377
- chore: compose da raiz repassa os limites de operador by @FelipeKreulich in #378
- release: compose repassa limites de operador by @FelipeKreulich in #379
- docs: termos de uso do CipherMesh Hub (EN + PT) by @FelipeKreulich in #381
- release: termos do hub + deploy automático by @FelipeKreulich in #383
- fix: /doctor usa a porta que o cliente realmente usaria by @FelipeKreulich in #384
- fix: /doctor distingue certificado de outro host de self-signed by @FelipeKreulich in #385
- release: correções do /doctor com domínio próprio by @FelipeKreulich in #386
- docs: hub público em ciphermesh.de by @FelipeKreulich in #387
- release: hub público em ciphermesh.de by @FelipeKreulich in #388
- fix: health check do deploy testava a porta errada by @FelipeKreulich in #389
- release: correção do health check do deploy by @FelipeKreulich in #390
- docs: READMEs atualizados (o do npm estava defasado) by @FelipeKreulich in #391
- release: 2.6.0 by @FelipeKreulich in #392
Full Changelog: v2.5.0...v2.6.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 withCannot find addonanywhere 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@latestdoes not use these files.