feat(fab26): wire in published FAB26 firmware build - #382
Conversation
Mirror the live manifest (api) into the bundled offline fallback: the
FAB26 Boston build shipped to event/fab26/firmware-2.7.27.d250d89, so
populate the firmware block and correct the slug from the provisional
fab2026 to the published fab26 (the flasher builds
event/{slug}/firmware-{version} from it).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 provides concrete metadata and release notes for firmware version ChangesEvent firmware metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes 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
Mirrors the live manifest (api PR) into the bundled offline fallback (
public/data/event_firmware.json), now that the FAB26 Boston build has shipped toevent/fab26/firmware-2.7.27.d250d89.Changes
firmwareblock: version2.7.27.d250d89, idv2.7.27.d250d89, title, zipUrl, event release notes (wasnull/ "coming soon").slugfrom the provisionalfab2026to the publishedfab26.utils/firmwareUrl.tsbuilds the download path asevent/${pathPrefix}/firmware-${version}, so the slug must match the real directory.Verification
The 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. Firmware block is byte-identical to the api manifest.🤖 Generated with Claude Code
Summary by CodeRabbit