GitHub deprecated Node.js 20 for actions; runners will force Node 24 by
June 2 2026. Opting in now via the documented FORCE_JAVASCRIPT_ACTIONS_TO_NODE24
env var instead of pinning every action version. Applied to both
firmware-build (PR check) and release (tag-driven) workflows.
Adds the project metadata and CI/release workflow needed to publish this
repo under Colorado-Mesh/meshcore-bot-firmware.
- LICENSE: MIT with attribution to upstream MeshCore (also MIT)
- README: rewritten with badges, supported boards, install paths (web
flasher / PlatformIO / esptool), bot command table, layout map,
development quickstart
- CONTRIBUTING: submodule + patch-queue workflow, what-goes-where,
patch hygiene rules, PR expectations
- RELEASE: cmesh-bot-vX.Y.Z tag scheme + procedure
- CHANGELOG: Keep-a-Changelog format, seeded with the hop-coordination
fix and patch-5 utility commands
- Issue templates: bug_report (with bot stats prompt), feature_request,
config.yml (no blank issues, link to upstream + community)
- Pull request template: layer checklist, verification gates,
prefs-schema impact prompt
- .github/workflows/firmware-build.yml: keep PR check on representative
envs (Heltec V3, RAK 4631 USB+BLE), add concurrency cancellation for
PRs, scope cache key to PIO config hash
- .github/workflows/release.yml: NEW; triggers on cmesh-bot-v* tag or
manual dispatch, enumerates all 133 *_companion_radio_(usb|ble) envs
from vendor/MeshCore/variants/, shards across 8 parallel matrix jobs,
aggregates artifacts into a single draft release
- scripts/verify.sh: respect MESHCORE_SKIP_APPLY_PATCHES like
build-representative.sh does, so verify works when vendor already has
patches applied as commits
- .gitignore: add .forge.bak.*/ for forge backup directories
