feat: update Burning Man 2026 firmware to 2.8.0.6fd990c

[thebentern]

Points the Burning Man 2026 edition at the newest event/burningmesh2026 build.

Built by CI run 31985534118 from event/burningmesh2026 @ 6fd990c, whose head commit is fix(mesh): dedup opaque relays to prevent an undecryptable-frame broadcast storm (meshtastic/firmware#11522) — worth having on a mesh the size of Black Rock City.

2.8.0.2651f28 → 2.8.0.6fd990c

slug, zipUrl, releaseNotes, and generatedAt are unchanged — same 3-line shape as the previous two bumps.

Verification

Every URL the flasher resolves for this build returns 200 at event/burningmesh2026/firmware-2.8.0.6fd990c/: release_notes.md, firmware-2.8.0.6fd990c.json, and the per-target .mt.json files.

Spot-checked firmware-tlora-t3s3-epaper-2.8.0.6fd990c.mt.json — the board that boot-looped at DEF CON — and it carries mt-esp32s3-ota.bin at app1 with spiffs at 0x340000, which is what the manifest-driven path added in #395 reads. So this build flashes with the right filenames and offsets rather than falling through to the legacy convention-based path.

Event tests pass (32/32 across firmwareUrl, eventManifest, eventDevices, firmwareStore.eventMode).

Paired with the matching change in meshtastic/api, which is the source of truth this snapshot syncs from.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Updates
  • Updated the Burning Man 2026 firmware version and identifier to 2.8.0.6fd990c.
  • Refreshed the associated firmware title to reflect the new release.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
web-flasher	Ready	Preview	Aug 17, 2026 11:32am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b68f0fd7-1635-426e-9faa-90ddfe88d7b6

📥 Commits

Reviewing files that changed from the base of the PR and between 3ee1964 and 8dce4c4.

📒 Files selected for processing (1)

• public/data/event_firmware.json

Included review availability: Your plan includes up to 2 reviews per rolling hour; 1 remains after this review.

---

📝 Walkthrough

Walkthrough

The Burning Man firmware metadata now uses release 2.8.0.6fd990c for its version, identifier, and title.

Changes

Firmware metadata

Layer / File(s)	Summary
Update Burning Man firmware release public/data/event_firmware.json	The version, identifier, and title now reference 2.8.0.6fd990c instead of 2.8.0.2651f28.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 8dce4

This updates the Burning Man 2026 firmware build reference while preserving the existing event metadata shape; no actionable merge-blocking risk remains beyond normal checks and review.

Suggested reviewers: ayysasha

Poem

I’m a rabbit with firmware bright,
A fresh release hops into sight.
Three fields now share one name,
2.8.0.6fd990c claims the frame.
Hop, hop—metadata is right!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely identifies the firmware update and the new version.
Description check	✅ Passed	The description explains the firmware update, source build, verification steps, test results, and related changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}