eric 2198741132 ci(e2e): run simulator with current meshtastic client, not the stale 2.6.1 pin ...

Meshtasticator's requirements.txt pins meshtastic~=2.6.1, which predates the
meshtastic/meshtasticd image it drives; with the old client the simulator
never observed node TX packets (both e2e directions timed out). The official
meshtastic firmware_harness uses the current client against the same
simulator-mode meshtasticd, so install the sim deps with meshtastic floating
instead of the pinned requirements file.

2026-09-07 21:53:31 -07:00

..

meshtasticator-e2e.yaml

ci(e2e): run simulator with current meshtastic client, not the stale 2.6.1 pin

2026-09-07 21:53:31 -07:00

release.yaml

fix(ci): forward auth token across http->https redirect on release publish

2026-09-07 21:01:34 -07:00