rouse-context/.github
monkopedia-coder 2a04b5785b
Make release crash reports decodable: publish R8 mappings, keep r8-map-id in frames (#755) (#794)
* relay: keep R8 map id in stack-frame file slot through crash sanitizer (#755)

Release builds rewrite every frame's SourceFile to r8-map-id-<sha256>,
which the long-token redactor destroyed, so filed traces could not be
tied to a mapping. Exempt exactly that value, only in the file slot of
a \tat frame line; everything else is still redacted. Adds an
R8-shaped sample trace and tests for the exemption and its limits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YYSPuh9bZEJkrzvnEpY1QK

* release: publish each variant's R8 mapping as a release asset (#755)

The mapping is the only way to decode a release build's crash traces,
and it died with the ephemeral runner. Stage foss and google mappings
(the FOSS one before the Google build's clean deletes it), verify each
against its staged APK by r8-map-id, and attach both to the GitHub
release with fail_on_unmatched_files so a missing one fails the job.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YYSPuh9bZEJkrzvnEpY1QK

---------

Co-authored-by: monkopedia-coder <monkopedia-coder@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 11:01:30 -04:00
..
ISSUE_TEMPLATE Fix #120: Add 'Report a bug' action in Settings 2026-04-14 19:33:19 -04:00
workflows Make release crash reports decodable: publish R8 mappings, keep r8-map-id in frames (#755) (#794) 2026-10-19 11:01:30 -04:00