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 a client 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.

This repo is the source of truth; the web-flasher's bundled offline snapshot is updated to match in meshtastic/web-flasher#414.

🤖 Generated with Claude Code

Summary by CodeRabbit

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

[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: 9e5630e5-b126-4375-8735-89beeec13482

📥 Commits

Reviewing files that changed from the base of the PR and between 189c61b and 75d957c.

📒 Files selected for processing (1)

• data/eventFirmware.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Burning Man 2026 firmware metadata now uses release 2.8.0.9334cd3 for its version, identifier, and display title.

Changes

Firmware metadata

Layer / File(s)	Summary
Update Burning Man firmware release data/eventFirmware.json	The Burning Man 2026 firmware version, identifier, and display title changed from 2.8.0.6fd990c to 2.8.0.9334cd3.

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

Merge Risk: ⚪ Minimal · up to 75d95

This localized firmware version update is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

Possibly related PRs

• meshtastic/api#112: Updates event-specific firmware metadata in the same file.
• meshtastic/api#117: Modifies the Burning Man 2026 firmware entry.
• meshtastic/api#118: Updates the successive Burning Man firmware reference.

Suggested reviewers: jamesarich, ayysasha

Poem

A rabbit checks the firmware sign,
“The Burning Man release is fine.”
Version, title, identifier align,
2.8.0.9334cd3 now shines.
Hop, hop—metadata is up to date!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the firmware version update for Burning Man 2026.
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.}