Protobuf Update Available
A new version of Meshtastic protobufs has been released.
|
Version |
| Current |
v2.7.22 |
| Latest |
v2.7.23 |
Update Instructions
Run the following commands in order:
# 1. Regenerate protobufs from upstream.
./scripts/generate_protos.sh update v2.7.23
# 2. Refresh the upstream hardware catalog (used by device_hardware_catalog.dart
# for hwModel → architecture mapping in the firmware update flow).
./scripts/fetch_device_hardware.sh
# 3. Run the parity test — this is the signal for whether the supplement
# in lib/services/firmware/device_hardware_catalog.dart needs editing.
flutter test test/services/firmware/hardware_architecture_test.dart
If step 1 prints ✅ Protobuf generation complete! but git status lib/generated/ shows nothing changed, run ./scripts/generate_protos.sh generate once more — the noisy pub-cache output can mask a silently-skipped codegen step.
Release Notes
View the release notes at:
https://github.com/meshtastic/protobufs/releases/tag/v2.7.23
Checklist
See CLAUDE.md → "Meshtastic Protobuf Updates" for the full workflow and rationale.
This issue was automatically created by the protobuf update checker.
Protobuf Update Available
A new version of Meshtastic protobufs has been released.
v2.7.22v2.7.23Update Instructions
Run the following commands in order:
If step 1 prints
✅ Protobuf generation complete!butgit status lib/generated/shows nothing changed, run./scripts/generate_protos.sh generateonce more — the noisy pub-cache output can mask a silently-skipped codegen step.Release Notes
View the release notes at:
https://github.com/meshtastic/protobufs/releases/tag/v2.7.23
Checklist
./scripts/generate_protos.sh update v2.7.23— verifyprotos/VERSIONandlib/generated/meshtastic/changed./scripts/fetch_device_hardware.sh— review any reported architecture mismatches or redundant supplement entriesflutter test test/services/firmware/hardware_architecture_test.dart— if a newHardwareModellacks coverage, add it to_supplementinlib/services/firmware/device_hardware_catalog.dart; if architecture is unclear, map toDeviceArchitecture.unknown(never guess)lib/generated/meshtastic/for unexpected field reorderingsdefault:inlib/services/protocol/protocol_service.dartportnum switch)Closes #<issue>in the commit message to auto-close)See
CLAUDE.md→ "Meshtastic Protobuf Updates" for the full workflow and rationale.This issue was automatically created by the protobuf update checker.