OpenCode/MeshBot
2
0
Fork 0
Code Issues Pull Requests Actions Activity

feat: pin sends to testowy channel index 2 via MESH_SEND_CHANNEL (v0.1.3)
CI / build + unit (pull_request) Successful in 1m3s
Details

Browse Source
This commit is contained in:
kamilkrzywda
2026-09-23 20:00:49 +00:00
parent 266aadf635
commit bbdc7e997a
7 changed files with 72 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+4
View File
@@ -1,5 +1,9 @@
# Changelog
## v0.1.3 — 2026-09-23 19:58
- Sends are now pinned to the test channel `testowy` (channel index 2) instead of the hardcoded primary channel (`channel: 0`). The target channel is configurable via `MESH_SEND_CHANNEL` (default `2`) and parsed once at service construction; `buildTextToRadio` takes the channel index as a parameter. Unit tests now decode the outbound ToRadio frame on the fake bridge and assert `packet.channel === 2` on the default send path.
## v0.1.2 — 2026-09-23 19:51
- Added a Gitea Actions CI pipeline (`.gitea/workflows/ci.yml`), mirroring flight's runner conventions: on push/PR to `main` (plus manual dispatch) one job runs `npm ci`, `nest build`, the vitest unit suite, and a production Docker image build — with retry loops for the runner's flaky uplink. No app code changed.