cj-vana 5af562c6be ci: pin submodule to upstream base and apply patches at build time ...

The submodule had been pointing at a local MeshCore commit that included
all 5 patches applied on top of upstream. That commit only exists in the
local working tree — CI's `submodules: recursive` checkout couldn't
fetch it from github.com/meshcore-dev/MeshCore and failed with
"fatal: not our ref d2ad3ac8".

Resets vendor/MeshCore to upstream main (910b1bee, the same base our
patches were authored against) so CI can fetch it normally, and adds an
explicit `apply-patches.sh` step to the firmware-build workflow before
the verify and build steps run. The release workflow already applies
patches explicitly so no change there.

Subsequent verify/build steps set MESHCORE_SKIP_APPLY_PATCHES=1 to avoid
re-applying patches on the now-dirty tree.

2026-05-16 13:05:24 -06:00

..

firmware-build.yml

ci: pin submodule to upstream base and apply patches at build time

2026-05-16 13:05:24 -06:00

release.yml

Add repo scaffolding for Colorado-Mesh publish

2026-05-16 13:01:09 -06:00