move the chip pin to v1.3.0 - #19
Merged
Merged
Conversation
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q9HbD44EKWWTRYgxbFGxf6
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.mdand theconsumersCI job were written for, and this is the first time the rule hascaught anything: the pin lagged from the moment the byte-path ABI merged, and
nothing here failed or complained.
What comes with it
their controllers clock one byte and want the answering byte back before the
next; a native node has the whole command in a buffer and does not use it.
test_model.cpphad reached 537 lines against thatrepository's own 500-line limit, so its CI had been red since before the
extraction.
v1.3.0could not be cut at all:GitHub retired the
macos-13runner, so that row queued for ever and took thepublish job with it.
Checked
simple_repeaterbuilds for linux-amd64 against this. A native node compilesthe model in, which is what keeps it the same chip the emulators load, from the
same commit.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Q9HbD44EKWWTRYgxbFGxf6