publish: getsentry/sentry-cli@3.3.4

[sentry-release-bot]

Requested by: @NicoHinderling

Merge target: (default)

Quick links:

• View changes
• View check runs

Assign the accepted label to this issue to approve the release.

Targets

• gcs
• npm[@sentry/cli-darwin]
• npm[@sentry/cli-linux-arm]
• npm[@sentry/cli-linux-arm64]
• npm[@sentry/cli-linux-i686]
• npm[@sentry/cli-linux-x64]
• npm[@sentry/cli-win32-i686]
• npm[@sentry/cli-win32-x64]
• npm[@sentry/cli-win32-arm64]
• npm[@sentry/cli]
• brew
• github
• registry
• pypi
• sentry-pypi
• docker[Docker Hub (release)]
• docker[Docker Hub (latest)]

Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.

---

📋 Changelog

New Features ✨

• Add sentry-cli build download command to download installable builds (IPA/APK) by build ID (#3221).
• Add sentry-cli code-mappings upload command to bulk upload code mappings from a JSON file (#3207, #3208, #3209, #3210).
  • Code mappings link stack trace paths (e.g. com/example/module) to source paths in your repository (e.g. src/main/java/com/example/module), enabling Sentry to display source context and link directly to your code from error stack traces.
  • Repository name and default branch are automatically inferred from your local git remotes, or can be specified explicitly with --repo and --default-branch.
  • Large mapping files are automatically split into batches for upload.

[github-actions]

Publishing: run#23564225791

[github-actions]

Failed to publish. (run logs)

Bad branch? You can delete with ease and start over.