Skip to content

chore(deps): update dependency @sentry/cli to v3#182

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/sentry-cli-3.x
Open

chore(deps): update dependency @sentry/cli to v3#182
renovate[bot] wants to merge 1 commit intomainfrom
renovate/sentry-cli-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Dec 21, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@sentry/cli (source) 2.5.0 → 3.3.5 age confidence

Release Notes

getsentry/sentry-cli (@​sentry/cli)

v3.3.5

Compare Source

Performance
  • (snapshots) Parallelize image hashing with rayon (#​3250)
Fixes
  • (sourcemaps) Skip non-base64 embedded sourcemaps during injection (#​3243)

v3.3.4

Compare Source

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.

v3.3.3

Compare Source

Internal Changes 🔧
  • (npm) 🤖 Bump optional dependencies to 3.3.2 in afdef906

v3.3.2

Compare Source

New Features ✨
Internal Changes 🔧
  • (npm) 🤖 Bump optional dependencies to 3.3.1 in 3200dfb9

v3.3.1

Compare Source

Fixes
  • Accept ProGuard mapping files without line information instead of rejecting them (#​3192).
  • Improve error message when uploading .xcarchive or .ipa files on non-Apple Silicon Macs (#​3211).
Experimental Feature 🧑‍🔬 (internal-only)
  • Pipe snapshot sidecar metadata into upload as part of sentry-cli build snapshots command (#​3163).

v3.3.0

Compare Source

New Features
  • Added sentry-cli proguard uuid <PATH> to compute and print the UUID for a ProGuard mapping file (#​3176).
Improvements
  • Moved sentry-cli upload-proguard to sentry-cli proguard upload, aligning the API with similar upload commands like debug-files upload and sourcemaps upload (#​3174). sentry-cli upload-proguard remains supported as an alias, so no migration is required.
Experimental Feature 🧑‍🔬 (internal-only)
  • Print snapshot URL after successful upload (#​3167).

v3.2.3

Compare Source

Experimental Feature 🧑‍🔬 (internal-only)
  • Added experimental sentry-cli build snapshots command to upload build snapshots to a project (#​3110).
    • This command uploads files from a specified directory to Sentry's Objectstore, associating them with a snapshot identifier.
    • The command is experimental and subject to breaking changes or removal in future releases.

v3.2.2

Compare Source

Fixes
  • Updated minimatch dependency to fix a vulnerability (#​3153)

v3.2.1

Compare Source

Fixes
  • The dart-symbol-map upload command now correctly resolves the organization from the auth token payload (#​3065).
  • Retry DNS resolution failures for sentry.io requests to reduce intermittent failures for some users (#​3085)

v3.2.0

Compare Source

Features
  • Add sourceMaps.inject() for injecting debug IDs (#​3088)
  • Add --install-group parameter to sentry-cli build upload for controlling update visibility between builds (#​3094)
Fixes
  • Recognize *.ghe.com URLs as github_enterprise VCS provider (#​3127).
  • Fixed a bug where the dart-symbol-map command did not accept the --url argument (#​3108).
  • Add timeout to build upload polling loop to prevent infinite loop when server returns unexpected state (#​3118).

v3.1.0

Compare Source

New Features
  • In the JavaScript API, added multi-project support to releases.newDeploy() method. This method now accept a projects option (array of project slugs), aligning them with the Rust CLI's multi-project capabilities and matching the existing behavior of releases.new() and releases.uploadSourceMaps() (#​3001).
Improvements
  • This release includes some changes to enable support for older self-hosted Sentry versions. With these changes, Sentry CLI now officially self-hosted Sentry versions 24.11.1 and above (#​3070)
Fixes
  • Fixed a bug that prevented project IDs from being used with the sentry-cli releases new command for users with self-hosted Sentry instances on versions older than 25.12.1 (#​3068).
  • Fixed a bug, introduced in version 3.0.0, where the sentry-cli releases list command ignored the --project option (#​3048). The command now correctly can filter releases by a single project when supplied via --project. This change does not enable filtering by multiple projects, which has never been supported.

v3.0.3

Compare Source

Fixes
  • Fixed a bug on Intel-based macOS systems that prevented Sentry CLI from respecting self-signed certificates trusted in the macOS keychain (#​3059).

v3.0.2

Compare Source

Fixes
  • Fixed a bug on ARM-based macOS systems that prevented Sentry CLI from respecting self-signed certificates trusted in the macOS keychain (#​3057).
Versioning Policy Update

Our versioning policy has reclassified the minimum supported self-hosted Sentry version as being part of the public API. Therefore, we will only increase this minimum supported self-hosted Sentry version in a major release of Sentry CLI.

v3.0.1

Compare Source

Performance Improvements
  • We switch to a faster compression algorithm (zstd) for uploading size analysis builds (sentry build upload) in preparation for this week's beta release! (#​3038)
Versioning Policy Update

Our versioning policy has reclassified the minimum supported self-hosted Sentry version as being part of the public API. Therefore, we will only increase this minimum supported self-hosted Sentry version in a major release of Sentry CLI.

v3.0.0

Compare Source

New Sentry Support Policy

sentry-cli 3.0.0 and above only officially supports Sentry SaaS and Sentry self-hosted versions 25.11.1 and higher. While many Sentry CLI features may, in practice, continue working with some older Sentry versions, continued support for Sentry versions older than 25.11.1 is not guaranteed. Changes which break support for Sentry versions below 25.11.1 may occur in minor or patch releases.

New Versioning Policy

Sentry CLI now defines a semantic versioning policy. We did not explicitly define a versioning policy previously, and this new policy should give more clarity about what can change in minor or patch releases versus what requires a major version bump.

Breaking Changes
  • Removed all sentry-cli files ... and sentry-cli releases files ... subcommands (#​2956). These commands provided functionality for managing release files, a feature that has been deprecated in Sentry. Users still using sentry-cli files upload to upload source maps should migrate to sentry-cli sourcemaps upload.
  • Removed the sentry-cli sourcemaps explain command (#​2947). The command had been deprecated for some time, since Sentry now has a better in-product debugging flow for source map problems via the "Unminify Code" button, which is displayed on any JavaScript issues which could not be unminified.
  • Removed the sentry-cli send-metric ... subcommands (#​3006). These commands have been deprecated, and the data they send is no longer accepted by Sentry.
  • Removed support for the legacy API key authentication method (#​2935). Sentry CLI now only supports authenticating with Auth Tokens. If you are using API key authentication via any of the following methods, you need to generate and use an Auth Token, instead:
    • --api-key CLI flag
    • SENTRY_API_KEY environment variable
    • api_key configuration file field
    • apiKey option in the JavaScript API
  • Removed the upload-proguard subcommand's --app-id, --version, --version-code, --android-manifest, and --platform arguments (#​2876, #​2940, #​2948). Users using these arguments should stop using them, as they are unnecessary. The information passed to these arguments is no longer visible in Sentry.
  • Removed the --started argument from the sentry-cli releases finalize command (#​2972). This argument is a no-op, so any users using it should simply stop using it.
  • Removed the --use-artifact-bundle flag from sentry-cli sourcemaps upload (#​3002). The flag was a no-op that only emitted a deprecation warning.
Node.js Wrapper Breakages

The following changes only apply when using sentry-cli via the npm package @sentry/cli:

  • The SentryCli.execute method's live parameter now only takes boolean values (#​2971). Setting live to true now behaves like 'rejectOnError' did previously, with a zero exit status resolving the returned promise with "success (live mode)" and a non-zero status rejecting the promise with an error message.

  • The option parameter to Releases.uploadSourceMaps no longer takes a live property (#​2971). We now always execute the command with live set to true.

  • Removed the apiKey option from SentryCliOptions (#​2935). If you are using apiKey, you need to generate and use an Auth Token via the authToken option, instead.

  • Removed the useArtifactBundle option from SentryCliUploadSourceMapsOptions (#​3002). This deprecated option was a no-op that users should simply stop passing.

  • Drop support for Node.js <18. The minimum required Node.js version is now 18.0.0 (#​2985).

  • The type export SentryCliReleases has been removed.

  • The JavaScript wrapper now uses named exports instead of default exports (#​2989). You need to update your imports:

    // Old (default import)
const SentryCli = require('@&#8203;sentry/cli');

// New (named import)
const { SentryCli } = require('@&#8203;sentry/cli');

    For ESM imports:

    // Old
import SentryCli from '@&#8203;sentry/cli';

// New
import { SentryCli } from '@&#8203;sentry/cli';
Improvements
  • The sentry-cli upload-proguard command now uses chunked uploading by default (#​2918). Users who previously set the SENTRY_EXPERIMENTAL_PROGUARD_CHUNK_UPLOAD environment variable to opt into this behavior no longer need to set the variable.
  • We now place source map debug IDs under the source map's debugId field, per the TC39 Debug ID proposal (#​3005). This change affects the sentry-cli sourcemaps inject command and, unless --no-rewrite is passed, the sentry-cli sourcemaps upload command. Sentry CLI can still read the debug_id field, but whenever the CLI writes or rewrites a source map, we always use debugId.
  • The sentry-cli build upload command now automatically tracks Sentry plugin versions from the SENTRY_PIPELINE environment variable (#​2994). When SENTRY_PIPELINE contains a recognized Sentry plugin (e.g., sentry-gradle-plugin/4.12.0 or sentry-fastlane-plugin/1.2.3), the plugin version is written to the .sentry-cli-metadata.txt file in uploaded build archives, enabling the backend to store metadata for size analysis and build distribution tracking.
Fixes
  • Fixed misleading error message claiming the server doesn't support chunk uploading when the actual error was a non-existent organization (#​2930).

v2.58.5

Compare Source

Fixes
  • Updated minimatch dependency to fix a vulnerability (#​3152)

v2.58.4

Compare Source

Fixes
  • Use node directly in the postinstall script, instead of using npm run (#​3030). This change ensures the postinstall script remains compatible with package managers other than npm.

v2.58.3

Compare Source

Improvements
  • For the sentry-cli build upload command, we now only auto-detect Git metadata when we detect we are running in a CI environment, unless the user manually overrides this behavior (#​2974). This change prevents local development builds from triggiering GitHub status checks for size analysis.
    • We can detect most common CI environments based on the environment variables these set.
    • We introduced two new arguments, --force-git-metadata and --no-git-metadata, which force-enable and force-disable automatic Git data collection, respectively, overriding the default behavior.
  • The sentry-cli build upload command now automatically detects the correct branch or tag reference in non-PR GitHub Actions workflows (#​2976). Previously, --head-ref was only auto-detected for pull request workflows. Now it works for push, release, and other workflow types by using the GITHUB_REF_NAME environment variable.
Fixes
  • Fixed a bug where the sentry-cli sourcemaps inject command could inject JavaScript code into certain incorrectly formatted source map files, corrupting their JSON structure (#​3003).

v2.58.2

Compare Source

Improvements
  • Added validation for the sentry-cli build upload command's --head-sha and --base-sha arguments (#​2945). The CLI now validates that these are valid SHA1 sums. Passing an empty string is also allowed; this prevents the default values from being used, causing the values to instead be unset.
Fixes
  • Fixed a bug where providing empty-string values for the sentry-cli build upload command's --vcs-provider, --head-repo-name, --head-ref, --base-ref, and --base-repo-name arguments resulted in 400 errors (#​2946). Now, setting these to empty strings instead explicitly clears the default value we would set otherwise, as expected.

v2.58.1

Compare Source

Deprecations
  • Deprecated API key authentication (#​2934, #​2937). Users who are still using API keys to authenticate Sentry CLI should generate and use an Auth Token instead.
Improvements
  • The sentry-cli debug-files bundle-jvm no longer makes any HTTP requests to Sentry, meaning auth tokens are no longer needed, and the command can be run offline (#​2926).
Fixes
  • Skip setting base_sha and base_ref when they equal head_sha during auto-inference, since comparing a commit to itself provides no meaningful baseline (#​2924).
  • Improved error message when supplying a non-existent organization to sentry-cli sourcemaps upload. The error now correctly indicates the organization doesn't exist, rather than incorrectly suggesting the Sentry server lacks artifact bundle support (#​2931).

v2.58.0

Compare Source

New Features
  • Removed experimental status from the sentry-cli build upload commands (#​2899, #​2905). At the time of this release, build uploads are still in closed beta on the server side, so most customers cannot use this functionality quite yet.
  • Added CLI version metadata to build upload archives (#​2890).
Deprecations
  • Deprecated the upload-proguard subcommand's --platform flag (#​2863). This flag was a no-op for some time, so we will remove it in the next major.
  • Deprecated the upload-proguard subcommand's --android-manifest flag (#​2891). This flag was a no-op for some time, so we will remove it in the next major.
  • Deprecated the sentry-cli sourcemaps upload command's --no-dedupe flag (#​2913). The flag was no longer relevant for sourcemap uploads to modern Sentry servers and was made a no-op.
Fixes
  • Fixed autofilled git base metadata (--base-ref, --base-sha) when using the build upload subcommand in git repos. Previously this worked only in the context of GitHub workflows (#​2897, #​2898).
Performance
  • Slightly sped up the sentry-cli sourcemaps upload command by eliminating an HTTP request to the Sentry server, which was not required in most cases (#​2913).

v2.57.0

Compare Source

New Features
  • (JS API) Add projects field to SentryCliUploadSourceMapsOptions (#​2856)
Deprecations
  • Deprecated the upload-proguard subcommand's --app-id, --version, and --version-code flags (#​2852), as we plan to remove these flags in Sentry CLI 3.x. Users should simply stop using the flags; the values specified there have never had an effect on deobfuscation, and are no longer visible in Sentry.
  • Added a deprecation notice for release bundle uploads, a legacy method for uploading source maps (#​2844). Release bundle uploads will be removed in Sentry CLI 3.x in favor of artifact bundles, the newer source map upload method introduced in Sentry version 23.6.2. Self-hosted users: You must upgrade to Sentry 23.6.2 or later before upgrading to Sentry CLI 3.x.
Fixes
  • Fixed a bug where some log messages would not show up in CI environments or when redirecting stderr to a file (#​2830). Specifically, this bug was affecting any subcommand that uses a progress bar, such as sentry-cli debug-files bundle-jvm and sentry-cli sourcemaps upload. Any stderr output during the progress bar was lost if stderr was redirected.

v2.56.1

Compare Source

Deprecations
  • Added a deprecation notice for legacy uploading methods (#​2836, #​2837)
    • Support for these legacy uploading methods, required to upload to self-hosted Sentry servers below version 10.0.0, will be removed in the next major release (3.x). If you observe these new deprecation notices, we recommend upgrading your self-hosted Sentry server, or pinning Sentry CLI to a compatible version (2.x).
    • You may encounter these deprecation notices when uploading debug files or sourcemaps.
Fixes & improvements
  • Fixed a bug with sourcemap injection (#​2764) by @​szokeasaurusrex
    • This change ensures we do not attempt to associate multiple compiled sources with the same sourcemap. As there should be at most one sourcemap for each compiled source, associating multiple compiled sources with the same sourcemap would lead to an invalid state.
  • Updated some outdated dependencies (#​2816, #​2818, and #​2819)

v2.56.0

Compare Source

Various fixes & improvements

v2.55.0

Compare Source

Various fixes & improvements

v2.54.0

Compare Source

Various fixes & improvements

v2.53.0

Compare Source

Various fixes & improvements
Changes from 2.53.0-alpha

2.53.0-alpha reintroduced the build (previously named mobile-app) commands. 2.53.0 is the first stable release to reintroduce them.

Please note, the build commands are still experimental, and are therefore subject to breaking changes, including removal, in any release, without notice.

v2.52.0

Compare Source

Various fixes & improvements

v2.51.1

Compare Source

Various fixes & improvements

v2.51.0

Compare Source

Logs command

This release introduces a new sentry-cli logs list command, which lists your Sentry logs. For more details, see sentry-cli logs list --help.

Please note: if you receive a 403 error when using the new command, you may need to generate a new auth token with different permissions. You can do this by navigating to Settings → Developer Settings → Personal Tokens in Sentry. On the Personal Tokens page, generate a token with org:read scope, and pass this to the command using --auth-token or by setting the SENTRY_AUTH_TOKEN environment variable.

Various fixes & improvements

v2.50.2

Compare Source

This change removes the mobile-app upload experimental feature which was introduced in 2.50.1.

v2.50.1

Compare Source

Various fixes & improvements
New experimental feature

This release introduces the new experimental mobile-app upload subcommand. This command is experimental, and therefore subject to changes, including breaking changes and/or removal, in any release. The command might not work as expected.

v2.50.0

Compare Source

Various fixes & improvements
  • feat(js): Expose rejectOnError in public execute type declarations (#​2628) by @​Lms24

v2.49.0

Compare Source

Various fixes & improvements
  • feat(js): Export live option type for releases.uploadSourceMaps (#​2627) by @​Lms24

v2.48.0

Compare Source

Various fixes & improvements
  • feat(js): Add live: 'rejectOnError' execution mode to execute method (#​2605) by @​Lms24
Build-time changes

v2.47.1

Compare Source

No user-facing changes.

v2.47.0

Compare Source

Various fixes & improvements

v2.46.0

Compare Source

Various fixes & improvements

v2.45.0

Compare Source

New feature
  • feat(sourcemaps): Multi-project sourcemaps upload (#​2497) by @​szokeasaurusrex
    • Sourcemaps can now be uploaded to multiple projects at once by passing each project to the sentry-cli sourcemaps upload command, like so: 
      sentry-cli sourcemaps upload -p project1 -p project2 /path/to/sourcemaps
    • Note that users on old versions of self-hosted Sentry may need to upgrade their self-hosted server to a newer version to take advantage of multi-project uploads.
Various fixes & improvements

v2.44.0

Compare Source

Various fixes & improvements

v2.43.1

Compare Source

Various fixes & improvements

v2.43.0

Compare Source

This release explicitly deprecates the sentry-cli debug-files upload command's --info-plist argument, since the argument does nothing. If you are using the --info-plist argument, you should stop using it.

Various fixes & improvements

v2.42.5

Compare Source

This is a re-release of 2.45.5-alpha as a stable release. There are no code changes from 2.45.5-alpha, since the Windows ARM build for that version was published successfully.

v2.42.4

Compare Source

Various fixes & improvements

v2.42.3

Compare Source

Various fixes & improvements
  • fix(sourcemaps): Fix mismatches between path and URL on Windows (#​2414) by @​BYK

v2.42.2

Compare Source

Various fixes & improvements

v2.42.1

Compare Source

This release is a re-release of 2.42.0. There are no code changes to the CLI. We are performing this re-release because 2.42.0 failed to publish to Docker Hub.

Various fixes & improvements

v2.42.0

Compare Source

With this release, we now build and publish multi-architecture (arm64 and aarch64) Docker images for Sentry CLI.

Various fixes & improvements

Non-user-facing changes

Configuration

📅 Schedule: Branch creation - "on the first day of the week" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/sentry-cli-3.x branch 3 times, most recently from bda50fc to 6a655d7 Compare January 12, 2026 16:35
@renovate renovate bot force-pushed the renovate/sentry-cli-3.x branch from 6a655d7 to f3b0f4b Compare February 9, 2026 14:32
@renovate renovate bot force-pushed the renovate/sentry-cli-3.x branch 2 times, most recently from 80aaefa to ac2e914 Compare February 23, 2026 18:44
@renovate renovate bot force-pushed the renovate/sentry-cli-3.x branch 2 times, most recently from f95c310 to 2342250 Compare March 4, 2026 17:40
@renovate renovate bot force-pushed the renovate/sentry-cli-3.x branch from 2342250 to 063c9da Compare March 14, 2026 14:27
@renovate renovate bot force-pushed the renovate/sentry-cli-3.x branch from 063c9da to 161e60e Compare March 31, 2026 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants