chore(proguard): Soft-deprecate the proguard upload --uuid flag#3177
Merged
szokeasaurusrex merged 3 commits intomasterfrom Mar 4, 2026
Merged
chore(proguard): Soft-deprecate the proguard upload --uuid flag#3177szokeasaurusrex merged 3 commits intomasterfrom
proguard upload --uuid flag#3177szokeasaurusrex merged 3 commits intomasterfrom
Conversation
2f4d2ac to
5c18fc3
Compare
szokeasaurusrex
added a commit
that referenced
this pull request
Mar 4, 2026
…3177) Using `--uuid` can cause unexpected behavior, if the same ProGuard mapping is uploaded with different UUIDs. Therefore, we now recommend using `proguard uuid` to obtain the UUID of a mapping before upload, as this eliminates the need to manually set a UUID. Stacked on #3176 Closes #3172 Closes [CLI-296](https://linear.app/getsentry/issue/CLI-296/proguard-upload-manually-specified-uuid-not-respected)
3c9f69d to
39b30e4
Compare
Add `sentry-cli proguard uuid <PATH>` to compute and print the UUID for a single ProGuard mapping file. This is the same UUID we use when uploading via `sentry-cli proguard upload` Stacked on #3175 Closes #3173 Closes [CLI-297](https://linear.app/getsentry/issue/CLI-297/expose-command-to-obtain-compute-uuid-for-proguard-mapping)
39b30e4 to
dcfaabf
Compare
szokeasaurusrex
added a commit
that referenced
this pull request
Mar 4, 2026
…3177) Using `--uuid` can cause unexpected behavior, if the same ProGuard mapping is uploaded with different UUIDs. Therefore, we now recommend using `proguard uuid` to obtain the UUID of a mapping before upload, as this eliminates the need to manually set a UUID. Stacked on #3176 Closes #3172 Closes [CLI-296](https://linear.app/getsentry/issue/CLI-296/proguard-upload-manually-specified-uuid-not-respected)
5c18fc3 to
ffc8502
Compare
…3177) Using `--uuid` can cause unexpected behavior, if the same ProGuard mapping is uploaded with different UUIDs. Therefore, we now recommend using `proguard uuid` to obtain the UUID of a mapping before upload, as this eliminates the need to manually set a UUID. Stacked on #3176 Closes #3172 Closes [CLI-296](https://linear.app/getsentry/issue/CLI-296/proguard-upload-manually-specified-uuid-not-respected)
dcfaabf to
0e765fb
Compare
romtsn
approved these changes
Mar 4, 2026
lcian
approved these changes
Mar 4, 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
3 participants
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.
Using
--uuidcan cause unexpected behavior, if the same ProGuard mapping is uploaded with different UUIDs.Therefore, we now recommend using
proguard uuidto obtain the UUID of a mapping before upload, as this eliminates the need to manually set a UUID.Stacked on #3176
Closes #3172
Closes CLI-296