feat: populate Open Sauce 2026 event firmware - #102
Conversation
The Open Sauce edition shipped with null firmware (coming soon). Fill in the customized build (v2.7.26.004b486, from the event/opensauce2026 branch), release notes, and theme name/tagline so the web-flasher serves a flashable build for opensauce.meshtastic.org.
|
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 OPEN_SAUCE edition entry in data/eventFirmware.json was updated to replace null placeholders with concrete values: theme name and tagline, plus firmware version, id, title, zipUrl, and releaseNotes specific to Open Sauce 2026. ChangesOpen Sauce edition metadata population
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
What
Fills in the Open Sauce 2026 edition's firmware and branding in
data/eventFirmware.json. It shipped with null firmware (rendered as "coming soon" in the web-flasher); this makes the edition serve a flashable build.firmware:v2.7.26.004b486(derived from theevent/opensauce2026branch), event-tailored release notes, and themeshtastic.github.io/event/opensauce2026/...zip URL.theme: name + tagline ("Where makers, science, and mesh collide.").iconUrlstays null — the web-flasher renders a dedicated Meshtastic × Open Sauce header lockup.Companion to meshtastic/web-flasher#370 (which mirrors this into the bundled offline snapshot and adds the header mode). This repo is the source of truth, so this PR is what makes the branding/firmware survive the web-flasher's background API refresh.
The firmware hash
004b486is theevent/opensauce2026branch HEAD, not a published artifact — the zip 404s until CI publishes tomeshtastic.github.io/event/opensauce2026/. Confirm the realversion/zipUrlbefore merging so attendees don't hit a 404.Summary by CodeRabbit