Skip to content

feat: update Burning Man 2026 event firmware - #406

Merged
thebentern merged 2 commits into
meshtastic:mainfrom
ayysasha:feat/burning-man-2026-event-firmware
Aug 13, 2026
Merged

feat: update Burning Man 2026 event firmware#406
thebentern merged 2 commits into
meshtastic:mainfrom
ayysasha:feat/burning-man-2026-event-firmware

Conversation

@ayysasha

@ayysasha ayysasha commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Sync the Burning Man 2026 bundled event-firmware manifest with the API metadata.
  • Use burn.meshtastic.org for first-load and offline event detection.
  • Point event flashing at published firmware 2.8.0.1cf8338 under burningmesh2026.
  • Add coverage showing that version and title metadata without a firmware ID remains non-flashable.

Validation

  • pnpm test:run — 188 tests passed.
  • pnpm build — passed.
  • TypeScript and JSON diagnostics — clean.
  • Published firmware manifest — HTTP 200.

Companion PR

Summary by CodeRabbit

  • New Features

    • Updated Burning Man 2026 event information, including dates, branding, resources, theme styling, firmware metadata, and release notes.
  • Bug Fixes

    • Improved handling of informational firmware editions without downloadable artifacts, preserving version details while omitting unavailable download links.

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
@vercel

vercel Bot commented Aug 13, 2026

Copy link
Copy Markdown

@ayysasha is attempting to deploy a commit to the Meshtastic Team on Vercel.

A member of the Team first needs to authorize it.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Review Change Stack

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: 044f3ea3-430c-4e70-a27e-8ddb8119e899

📥 Commits

Reviewing files that changed from the base of the PR and between c88025b and f454375.

📒 Files selected for processing (1)
  • public/data/event_firmware.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • public/data/event_firmware.json

📝 Walkthrough

Walkthrough

The manifest timestamp and Burning Man 2026 metadata were updated. Event resources, styling, and firmware release information were added. A regression test covers known firmware versions without permanent download artifacts.

Changes

Event firmware manifest

Layer / File(s) Summary
Manifest data and firmware availability coverage
public/data/event_firmware.json, utils/eventManifest.test.ts
The Burning Man 2026 entry now contains updated event metadata, resources, styling, firmware version details, and release notes. The regression test verifies that firmware without permanent artifacts remains informational.

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

Mergeability Score: ⚪ Minimal · up to f4543

This PR updates the Burning Man 2026 firmware manifest and adds coverage for non-flashable metadata; no actionable merge-blocking risk remains after normal checks.

Possibly related PRs

Poem

A rabbit updates the festival glow,
With firmware notes in a tidy row.
No download yet, the title stays bright,
New links and colors greet the night.
Hop, hop—the manifest is right!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely identifies the main change: updating the Burning Man 2026 event firmware.
Description check ✅ Passed The description clearly explains the changes and provides detailed validation results, including tests, build, diagnostics, and manifest verification.
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.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch

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

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

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
@thebentern
thebentern merged commit 8f18bd8 into meshtastic:main Aug 13, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants