From fa891eacf7405a94c267a7eb9d65092526000b90 Mon Sep 17 00:00:00 2001 From: R0ck Date: Fri, 4 Sep 2026 00:39:24 +0100 Subject: [PATCH] move the chip pin to v1.3.0 A submodule is a commit, not a branch, so four commits landed in MeshBench/virtual-sx1262 and reached nothing here. That is the whole hazard CONSUMERS.md and the consumers CI job were written for, and this is the first time the rule has caught anything: the pin lagged from the moment the byte-path ABI merged. What comes with it: the byte-at-a-time SPI path (ABI 1.3), which is what the emulators drive and which a native node does not use; the test file split, which had put that repository's CI red against its own 500-line limit; and the release matrix fix that let v1.3.0 be cut at all. A native node compiles the model in, which is what keeps it the same chip the emulators load from the same commit. simple_repeater builds for linux-amd64 against this. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Q9HbD44EKWWTRYgxbFGxf6 --- vendor/virtual-sx1262 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vendor/virtual-sx1262 b/vendor/virtual-sx1262 index 2b9145e..0debbb9 160000 --- a/vendor/virtual-sx1262 +++ b/vendor/virtual-sx1262 @@ -1 +1 @@ -Subproject commit 2b9145e7036fa66c5a9daa10d9b375017456e2a3 +Subproject commit 0debbb9125bbcc7eafb90aa6253bfa4ab3c435a9