feat: update Burning Man 2026 firmware to 2.8.0.9334cd3

[thebentern]

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

Built by CI run 32206334633 from event/burningmesh2026 @ 9334cd3.

2.8.0.6fd990c → 2.8.0.9334cd3

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

What's new since 2.8.0.6fd990c

• dbd6a31 — relay foreign packets whose channel hash collides with a local channel (#11544)
• 32563e0 — coerce coordinate traffic to the position channel on event builds (#11545)
• 2efff18 — make the coordinate-port RX expectation event-mode aware
• 9334cd3 — don't reference the position module on MESHTASTIC_EXCLUDE_GPS builds

The last one is a build fix for the coordinate-channel change; the three earlier attempts to build this branch were cancelled by successive pushes, so 9334cd3 is the first of them to publish.

Verification

The build directory holds 509 files, matching the previous build, so the publish is complete. Every URL the flasher resolves returns 200 at event/burningmesh2026/firmware-2.8.0.9334cd3/: release_notes.md, firmware-2.8.0.9334cd3.json, and the per-target .mt.json files.

Spot-checked firmware-tlora-t3s3-epaper-2.8.0.9334cd3.mt.json — mt-esp32s3-ota.bin at app1, spiffs at 0x340000 — the values the manifest-driven path from #395 reads, so this flashes with correct filenames and offsets.

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

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Updates
  • Updated the Burning Man 2026 firmware version, identifier, and title to 2.8.0.9334cd3.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
web-flasher	Ready	Preview	Aug 19, 2026 5:08am

[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: 22c66844-df64-4921-8e6a-ca9b9968aacd

📥 Commits

Reviewing files that changed from the base of the PR and between 279d1af and 7826b09.

📒 Files selected for processing (1)

• public/data/event_firmware.json

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

---

📝 Walkthrough

Walkthrough

Changes

Firmware metadata

Layer / File(s)	Summary
Update Burning Man firmware metadata public/data/event_firmware.json	The Burning Man 2026 firmware version, identifier, and title change from 2.8.0.6fd990c to 2.8.0.9334cd3.

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

Merge Risk: ⚪ Minimal · up to 7826b

This localized update points the Burning Man 2026 firmware entry to the new build while preserving the existing release metadata shape, with the referenced artifacts and event behavior validated; no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

• meshtastic/web-flasher#406: Updates the Burning Man 2026 firmware metadata in the same file.
• meshtastic/web-flasher#411: Updates the same Burning Man 2026 firmware metadata and supersedes the earlier firmware update.

Suggested reviewers: ayysasha

Poem

A rabbit checks the firmware leaf,
Finds a newer version beneath.
The title hops, the ID aligns,
Three small edits mark the signs.
“Flash ahead!” the rabbit cheers.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the firmware update and specifies the new Burning Man 2026 version.
Description check	✅ Passed	The description explains the update, lists included changes, and documents build verification and test results, although it omits the template checkboxes.
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.}