feat: add Burning Man 2026 event firmware

[ayysasha]

Summary

• Finalize Burning Man 2026 event dates, branding, theme, and documentation links.
• Use the production flasher hostname at burn.meshtastic.org.
• Publish the event artwork through the API.
• Point the event entry at firmware 2.8.0.1cf8338 under burningmesh2026.
• Include backup, update, and nRF52 factory-reset guidance.

Firmware

The expanded firmware artifacts are published at:

event/burningmesh2026/firmware-2.8.0.1cf8338/

zipUrl remains null because the web flasher consumes the published per-device manifests and binaries directly.

Validation

• Parsed data/eventFirmware.json.
• Verified burningman2026.png as a 1024×1024 PNG.
• Verified the published firmware manifest returns HTTP 200.
• Verified the corresponding web-flasher test suite and production build.

Companion PR

• feat: update Burning Man 2026 event firmware web-flasher#406

[coderabbitai]

Warning

Review limit reached

@ayysasha, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3abe00f3-9d9b-4f20-a926-b4954cd8761d

📥 Commits

Reviewing files that changed from the base of the PR and between 008fe34 and ba3ca24.

📒 Files selected for processing (1)

• data/eventFirmware.json

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: 1b6fe6d6-db2a-4465-91b9-3b888d6a6923

📥 Commits

Reviewing files that changed from the base of the PR and between 78cdbce and 008fe34.

⛔ Files ignored due to path filters (1)

• static/eventFirmware/burningman2026.png is excluded by !**/*.png

📒 Files selected for processing (1)

• data/eventFirmware.json

---

📝 Walkthrough

Walkthrough

The manifest generation timestamp was updated. The Burning Man 2026 entry now includes revised event details, links, theme metadata, and firmware release information.

Changes

Event firmware manifest

Layer / File(s)	Summary
Manifest and event metadata data/eventFirmware.json	The manifest timestamp was updated. The Burning Man 2026 entry now includes revised dates, branding, links, theme styling, firmware metadata, and release notes.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: 🔵 Low · up to 008fe

The event entry may show Burning Mesh as active on August 28, 2026, two days before the cited official event start of August 30, 2026. The PR is otherwise mergeable, but the date semantics should be confirmed or documented before merge.

Suggested reviewers: jamesarich, thebentern

Poem

A rabbit checked the manifest with care,
New Burning Man details now bloom there.
Links hop in line, firmware notes grow,
Dates and bright branding now show.
“Null download,” says the hare, “still stays!”

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding Burning Man 2026 event firmware support.

---

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.}