We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 12 since January 2026, each linked to its source.
sentry-cliWhen uploading an IPA with dSYM bundles, run `sentry-cli build upload` with `--dsym <PATH>` for each bundle, directory, or ZIP to include. This option is documented for IPA uploads.
sentry-cli build upload <ipa-path> --dsym <dsym-path>When comparing two local PNG snapshot directories, run `sentry-cli snapshots diff <base-dir> <head-dir>`; the command compares them using odiff.
sentry-cli snapshots diff <base-dir> <head-dir>When the repository needs Sentry baseline images, run `sentry-cli snapshots download` with the app ID and branch. The release note confirms the command downloads baseline snapshot images; the official release page does not document its flags.
For a selective snapshot build, supply the full test suite's image names to detect removals and renames. Run `sentry-cli snapshots upload <image-dir> --app-id <app-id>` with either `--all-image-file-names <comma-separated-names>` or `--all-image-file-names-file <path>`; each flag enables selective mode.
sentry-cli snapshots upload <image-dir> --app-id <app-id> --all-image-file-names '<image1>,<image2>'When Xcode release auto-discovery needs Info.plist preprocessing, run `sentry-cli releases propose-version --allow-xcode-infoplist-preprocessing` only for a trusted project; otherwise use the default, which disables preprocessing. The same flag is documented in `send-event`; the release note also names `bash-hook --send-event` and `react-native xcode` as affected.
sentry-cli releases propose-version --allow-xcode-infoplist-preprocessingWhen the snapshot directory contains only a subset of images, run `sentry-cli build snapshots` with `--selective` to mark the upload as selective. On PRs, removals and renames cannot be detected for selective uploads.
sentry-cli build snapshots <IMAGE_DIRECTORY> --app-id <APP_ID> --project <PROJECT_SLUG> --selectiveWhen bundling JVM sources from a project root, run `sentry-cli debug-files bundle-jvm` with the required input directory, output directory, and debug UUID; repeat `--exclude` for custom glob patterns. The v3.4.0 source also collects extensions beyond those listed in the release note, so the supported extension set is not fully documented here.
sentry-cli debug-files bundle-jvm <project-root> --output <output-dir> --debug-id <UUID> --exclude '<glob-pattern>'When the build is installable, run `sentry-cli build download --build-id <build_id>` to save its IPA or APK in the current directory. The command is experimental and requires an organization-scoped context and an `org:read` personal token.
sentry-cli build download --build-id <build_id>When configuring repository code mappings, create a nonempty JSON array of mappings with nonempty `stackRoot` and `sourceRoot` values, then run `sentry-cli code-mappings upload <PATH>` for the target organization. Repository and default branch can be inferred from local Git; set `--repo` and `--default-branch` explicitly when needed.
sentry-cli code-mappings upload <PATH> --org <ORG>When uploading preprod snapshots, use `build snapshots upload` and provide VCS metadata with the documented flags; the command also supports automatic metadata collection in most CI environments.
sentry-cli build snapshots upload --org <org> --project <project> <path> --app-id <app-id> --head-sha <head-sha> --base-sha <base-sha> --vcs-provider <provider> --head-repo-name <owner/repo> --base-repo-name <owner/repo> --head-ref <branch> --base-ref <branch> --pr-number <number>