p1neappleXpressandClaude Sonnet 5 38a65e5ab7 Self-host the node-install.sh source and add a general CLI release workflow ...

deploy/node-install.sh downloaded the exit-node core from
meepo161/openfluxfork's releases; point it at this repository's own
node-v* release instead (published by node-release.yml, unchanged
otherwise), and fix that workflow's Go version pin (1.26.8, stale vs.
go.mod's 1.26.4) so its reproducible build actually reproduces.

Add release.yml: a v* tag cross-compiles the CLI for every supported
platform and publishes it here, replacing the ad-hoc manual 0.0.x releases.

Drop docs/plans/*coordinated-node-release*: that design dispatched a
release in meepo161/openfluxfordesktop from a core tag here. The client
apps are now self-sufficient (their own submodule-pinned core, their own
release workflow), so the cross-repo dispatch it planned no longer applies.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-27 12:43:23 +03:00

..

plans

Self-host the node-install.sh source and add a general CLI release workflow

2026-09-27 12:43:23 +03:00

CONNECT.ru.md

integrate: fold openfluxfork features onto the encrypted-logging hotfix

2026-09-27 02:47:49 +03:00