feat: wire in published FAB26 firmware build - #106
Conversation
The FAB26 Boston build has shipped to
meshtastic.github.io/event/fab26/firmware-2.7.27.d250d89, so populate the
edition's firmware block (version/id/title/zipUrl/releaseNotes) that was
null ("coming soon").
Corrects the firmware slug from the provisional fab2026 to the published
fab26 — the flasher derives event/{slug}/firmware-{version} from it, so
it must match the real path.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe FAB26 Boston firmware entry now contains a ChangesFAB26 firmware update
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
The FAB26 Boston firmware build has been published to
meshtastic.github.io/event/fab26/firmware-2.7.27.d250d89. This populates the FAB26 edition'sfirmwareblock, which wasnull("coming soon") when the edition was first added.Changes
firmware.version→2.7.27.d250d89,id→v2.7.27.d250d89,title,zipUrl, and eventreleaseNotes.firmware.slugfrom the provisionalfab2026to the publishedfab26. The web-flasher derives its download path asevent/{slug}/firmware-{version}, so the slug must match the real directory.Verification
The exact path the flasher builds resolves:
raw.githubusercontent.com/meshtastic/meshtastic.github.io/master/event/fab26/firmware-2.7.27.d250d89/firmware-2.7.27.d250d89.json→ 200.Companion
event_firmware.jsonfallback so offline resolution flashes the shipped build too.🤖 Generated with Claude Code
Summary by CodeRabbit