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

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

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • Updated the Burning Man 2026 firmware version and identifier to 2.8.0.6fd990c.

[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: c013c00b-9512-479d-bea6-70a2626050b0

📥 Commits

Reviewing files that changed from the base of the PR and between 934c39c and 83459f9.

📒 Files selected for processing (1)

• data/eventFirmware.json

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

---

📝 Walkthrough

Walkthrough

The Burning Man 2026 firmware metadata now uses version 2.8.0.6fd990c and identifier v2.8.0.6fd990c.

Changes

Firmware metadata

Layer / File(s)	Summary
Update firmware metadata data/eventFirmware.json	Updated the Burning Man firmware version, identifier, and title from 2.8.0.2651f28 to 2.8.0.6fd990c.

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

Merge Risk: ⚪ Minimal · up to 83459

This is a localized firmware-version metadata update with no actionable merge-blocking risk remaining beyond normal checks and review.

Suggested reviewers: jamesarich, ayysasha

Poem

A rabbit hops through firmware fields,
New version marks the code it shields.
The title follows, neat and bright,
Burning Man metadata set right.
Three small lines now spring to life.

🚥 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 in the pull request.
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.}