chore(deps): Bump proguard to 5.10.3#1937
Merged
Merged
Conversation
Picks up the `ComposableSingletons$FileKt` source-file synthesis fix from getsentry/rust-proguard#94. The upstream crate carries unit and integration coverage for the new behavior; no symbolicator-side changes are needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Dav1dde
approved these changes
Apr 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
proguardfrom 5.10.2 to 5.10.3 to pick up theComposableSingletons$FileKtsource-file synthesis fix from getsentry/rust-proguard#94.When a Compose-generated
ComposableSingletons$MainActivityKtclass is inlined through an R8 synthetic lambda and no top-level class declaration exists for it in the mapping (common in Android builds), the previoussynthesize_source_filetruncated at the first$and producedComposableSingletons.java. 5.10.3 scans every$-segment for aKtmarker and now resolves toMainActivity.kt.No symbolicator-side changes are needed — the fix is entirely inside the leaf utility. Upstream carries unit tests (7 cases in
src/utils.rs) and an integration test (tests/r8-source-file-edge-cases.rs::test_composable_singletons_inlined_lambda_stacktrace). Skipping an end-to-end integration test here since there's no new data flow or wiring to exercise on this side; happy to add one if reviewers prefer.