feat: update DEF CON 34 firmware to 2.8.0.c800fc8 - #390
Conversation
Points the DEF CON 34 edition at the build that restores the custom boot logo on MUI hardware (device-ui pin held at ef573c3) and carries the signing/ingress hardening from firmware #11282. Was 2.8.0.8adc7c3. version / id / title / zipUrl bumped; slug and release notes unchanged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe DEF CON 34 firmware manifest entry now references build ChangesDEF CON 34 firmware
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@public/data/event_firmware.json`:
- Around line 126-129: The Meshtastic Firmware 2.8.0.c800fc8 entry currently
points to an unavailable artifact. Update its zipUrl to the published firmware
ZIP URL, and add the companion manifest URL or equivalent publishing-readiness
metadata once available; do not merge the entry while either artifact remains
unavailable.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: cc4f8d38-c8ed-496f-ad81-3e389ec90ae4
📒 Files selected for processing (1)
public/data/event_firmware.json
| "version": "2.8.0.c800fc8", | ||
| "id": "v2.8.0.c800fc8", | ||
| "title": "Meshtastic Firmware 2.8.0.c800fc8", | ||
| "zipUrl": "https://github.com/meshtastic/meshtastic.github.io/raw/master/event/defcon34/firmware-2.8.0.c800fc8.zip", |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
artifact_url='https://github.com/meshtastic/meshtastic.github.io/raw/master/event/defcon34/firmware-2.8.0.c800fc8.zip'
test "$(curl -L -s -o /dev/null -w '%{http_code}' "$artifact_url")" = 200Repository: meshtastic/web-flasher
Length of output: 160
🏁 Script executed:
#!/bin/bash
set -u
artifact_url='https://github.com/meshtastic/meshtastic.github.io/raw/master/event/defcon34/firmware-2.8.0.c800fc8.zip'
printf 'HEAD-only artifact status:\n'
curl -sSIL "$artifact_url" | sed -n '1,20p'
artifact_code="$(curl -L -s -o /dev/null -w '%{http_code}' "$artifact_url")"
printf '\nfollow-redirects artifact status code: %s\n' "$artifact_code"
printf '\nCandidate manifest URLs in repository:\n'
git ls-files '*manifest*' | sed -n '1,80p'
printf '\nRelevant event_firmware.json excerpt:\n'
sed -n '11,15p;120,135p' public/data/event_firmware.jsonRepository: meshtastic/web-flasher
Length of output: 6278
🌐 Web query:
github.com/meshtastic/meshtastic.github.io raw master event defcon34 firmware-2.8.0.c800fc8.zip
💡 Result:
The file path and naming convention you referenced corresponds to a specific firmware build for the Meshtastic project associated with DEF CON 34 [1]. The Meshtastic community maintains specialized event-specific firmware builds for DEF CON to provide tailored theming and functionality for attendees [2][3]. Technical details regarding the build, including the logo, brand palette, and event-specific theming, are managed within the Meshtastic repositories (such as the Meshtastic-Android project) [2]. DEF CON 34 is scheduled for August 6-9, 2026, in Las Vegas [4]. It is important to note that firmware files with version numbers like "2.8.0" also appear in various unrelated legacy contexts, such as DVD player firmware from 2003 or other unrelated software tools [5][6][7][8][9]; ensure any file you are using is sourced directly from the official Meshtastic GitHub repositories or verified community channels to avoid security risks or compatibility issues.
Citations:
- 1: https://github.com/meshtastic/web-flasher/actions/workflows/test.yml
- 2: feat(event): DEF CON 34 logo and full brand palette in event theming Meshtastic-Android#6483
- 3: https://meshtastic.org/blog/tags/defcon/
- 4: https://defcon.org/html/defcon-34/dc-34-vendors.html
- 5: https://www.touslesdrivers.com/index.php?v_code=4164&v_langue=en&v_page=23
- 6: http://repo.pureos.net/pureos/pool/main/a/arm-trusted-firmware/arm-trusted-firmware_2.8.0+dfsg-1.dsc
- 7: https://www.touslesdrivers.com/index.php?v_code=4163&v_page=23
- 8: https://docs.nordicsemi.com/bundle/zephyr-apis-2.8.0/page/dir_e97f19a49725d52aae6eece65b856a75.html
- 9: https://allflashfiles.net/2017/09/alcatel-one-touch-flash-tool-upgrade.html
🌐 Web query:
github.com/meshtastic/meshtastic.github.io event defcon34 manifest latest
💡 Result:
The Meshtastic project maintains event-specific firmware builds for DEF CON, identified in the firmware codebase as meshtastic_FirmwareEdition_DEFCON (enum value 17) [1]. For DEF CON 34, development and event-specific support included the integration of dedicated branding, such as the event logo and color palette into the Meshtastic Android application [2], as well as event-specific firmware distributions [3][4]. The meshtastic/meshtastic.github.io repository serves as a hosting point for release assets, including firmware files [5][6]. While the repository contains numerous automated commits for firmware updates [6][7][8][9], there is no single file explicitly named "defcon34 manifest." Instead, event-specific assets and firmware are bundled into the project's broader release and event-theming infrastructure [2][3]. Project documentation and assets related to DEF CON are tracked and updated as part of the standard release workflow and event-specific configurations [10][2]. Attendees at DEF CON 34 utilized standardized configurations, such as specific LoRa regions and channels, often coordinated through community resources like the Ham Radio Village [11].
Citations:
- 1: https://github.com/meshtastic/firmware/blob/b2bda3b0/src/mesh/generated/meshtastic/mesh.pb.h
- 2: feat(event): DEF CON 34 logo and full brand palette in event theming Meshtastic-Android#6483
- 3: https://github.com/meshtastic/web-flasher/actions/workflows/test.yml
- 4: https://git.redxen.eu/RepoMirrors/meshtastic-firmware/compare/develop...revert-10585-copilot/fix-failing-github-actions-job?show-outdated=&style=unified&whitespace=ignore-change
- 5: https://github.com/meshtastic/meshtastic.github.io
- 6: meshtastic/meshtastic.github.io@241abad
- 7: meshtastic/meshtastic.github.io@b211033
- 8: meshtastic/meshtastic.github.io@cf7317d
- 9: meshtastic/meshtastic.github.io@477698d
- 10: https://meshtastic.org/blog/tags/defcon/
- 11: https://conham.radio/dc
Do not merge while the firmware artifact is unavailable.
The configured zipUrl resolves to a GitHub HTML “404” page after redirects rather than the firmware ZIP, so clients can select this DEF CON entry but fail to download the software. Add the correct artifact URL—and publishing readiness information such as the companion manifest URL—when the asset is published.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@public/data/event_firmware.json` around lines 126 - 129, The Meshtastic
Firmware 2.8.0.c800fc8 entry currently points to an unavailable artifact. Update
its zipUrl to the published firmware ZIP URL, and add the companion manifest URL
or equivalent publishing-readiness metadata once available; do not merge the
entry while either artifact remains unavailable.
1 participant
Points the DEF CON 34 edition at the next published build:
event/defcon34/firmware-2.8.0.c800fc8(was2.8.0.b00d76f→2.8.0.8adc7c3).version/id/title/zipUrlbumped to2.8.0.c800fc8slugstaysdefcon34, so the flasher's derived pathevent/{slug}/firmware-{version}resolves to the new directoryWhat's in the new build
Two commits on top of
2.8.0.8adc7c3onevent/defcon34:8adc7c3shipped the stock Meshtastic logo on the T-Deck boot screen instead of the event logo. The branding pipeline was fine — the logo is byte-identical in both builds' littlefs images — but firmware MUI: Portduino curl maps firmware#11214 bumped device-ui to a commit that setsLV_USE_LODEPNG 0without registering its PNGdec replacement as an LVGL image decoder, leaving LVGL with no decoder for a PNG file source. The event branch now holds the device-ui pin atef573c3. Upstream: Custom boot logo no longer renders: LV_USE_LODEPNG=0 leaves LVGL without a PNG file decoder device-ui#357.⛔ Do not merge until the build publishes
The publishing run is in flight: firmware run 30500538943. Until it finishes,
event/defcon34/firmware-2.8.0.c800fc8/does not exist and merging this would point the flasher at a 404.Gate on this returning
200for both the manifest and a sample artifact:Local verification already done on the firmware side:
t-deck-tftbuilds clean at this SHA (flash 58.2% of the 6.5 MB app partition),lv_lodepng.c.ois linked in, and the DEF CON logo is present in the producedlittlefs-t-deck-tft-2.8.0.c800fc8.bin.Note (pre-existing, not changed here): the
zipUrlconvention —event/{slug}/firmware-{version}.zip— 404s for every edition, since github.io stores these builds as directories rather than a single zip. Carried forward as-is; worth a separate cleanup if nothing consumes it.Companion: meshtastic/api#112 updates the live manifest; this PR keeps the flasher's bundled fallback copy in sync. Merge both.
Summary by CodeRabbit