sentry_dart_plugin
Uploads debug symbols to Sentry for server-side symbolication.
3.4.0
568K downloads/mo
#480 most downloaded on pub.dev
getsentry/sentry-dart-plugin
What this package is like to depend on
Last release 2 months ago
28 May 2026
Release timing varies
gaps range from 1 weeks to 4 months
Nearly every release is documented
notes for 25 of 25 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
36 releases · first in 2021
4 releases in the last 12 months
see the full history below
Release timeline
36 releases · Aug 2021 to May 2026Releases
latest 36-
3.4.028 May 2026Release notes
Open source →Dependencies
- Bump sentry-cli to v2.58.6 by @szokeasaurusrex in #402
Fixes
Internal Changes
- (deps) Bump getsentry/craft from 2.19.0 to 2.25.2 by @dependabot in #390
- Notify linked issues on release by @buenaflor in #404
Release notes
Open source →Dependencies
- Bump sentry-cli to v2.58.6 by @szokeasaurusrex in #402
Fixes
- Prevent stale dart symbol map debug ID markers by @denrase in #403
Internal Changes
Release notes
Open source →Features
- (snapshots) Add
--selectiveflag tobuild snapshotsto indicate the upload contains only a subset of images (#3268) - (bundle-jvm) Allow running directly on a project root (including multi-module repos) by automatically collecting only JVM source files (
.java,.kt,.scala,.groovy), respecting.gitignore, and excluding common build output directories (#3260) - (bundle-jvm) Add
--excludeoption for custom glob patterns to exclude files/directories from source collection (#3260)
Performance
- (snapshots) Parallelize image hashing with rayon (#3250)
Fixes
- (snapshots) Chunk image uploads to avoid file descriptor exhaustion and 413 errors when uploading hundreds of images (#3249)
- (snapshots) Preserve subdirectory structure in snapshot manifest keys instead of flattening to bare filenames (#3269)
- Replace
eprintln!withlog::info!for progress bar completion messages when the progress bar is disabled (e.g. in CI). This avoids spurious stderr output that some CI systems treat as errors (#3223).
-
3.3.021 Apr 2026Release notes
Open source →Features
- Ignore path list for web (#340)
- You can use the
ignore_web_source_pathsfield: e.gignore_web_source_paths: [test/**/*.js] - This will ignore all specified files and directories from being uploaded
- You can use the
- Improve flavored Apple debug symbol discovery (#393)
Fixes
Release notes
Open source →Features
- Ignore path list for web (#340)
- You can use the
ignore_web_source_pathsfield: e.gignore_web_source_paths: [test/**/*.js] - This will ignore all specified files and directories from being uploaded
- You can use the
- Improve flavored Apple debug symbol discovery (#393)
Fixes
Release notes
Open 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-proguardtosentry-cli proguard upload, aligning the API with similar upload commands likedebug-files uploadandsourcemaps upload(#3174).sentry-cli upload-proguardremains supported as an alias, so no migration is required.
Experimental Feature 🧑🔬 (internal-only)
- Print snapshot URL after successful upload (#3167).
- Ignore path list for web (#340)
-
3.2.112 Jan 2026 -
3.2.030 Oct 2025Release notes
Open source →Features
- Upload Dart symbol mapping file (#347)
- Enables symbolication of Flutter issue titles for obfuscated builds.
- Supported: Android and iOS
- Not supported (yet): macOS, Linux and Windows.
- Generate the mapping file: Add
--extra-gen-snapshot-options=--save-obfuscation-map=<path>when building. Example:flutter build apk --obfuscate --split-debug-info=build/symbols --extra-gen-snapshot-options=--save-obfuscation-map=build/mapping.json - Configure the plugin: Set
dart_symbol_map_path: build/mapping.json - Important:
dart_symbol_map_pathmust point directly to the mapping file (absolute or relative path), not a directory.
Release notes
Open source →Features
- Upload Dart symbol mapping file (#347)
- Enables symbolication of Flutter issue titles for obfuscated builds.
- Supported: Android and iOS
- Not supported (yet): macOS, Linux and Windows.
- Generate the mapping file: Add
--extra-gen-snapshot-options=--save-obfuscation-map=<path>when building. Example:flutter build apk --obfuscate --split-debug-info=build/symbols --extra-gen-snapshot-options=--save-obfuscation-map=build/mapping.json - Configure the plugin: Set
dart_symbol_map_path: build/mapping.json - Important:
dart_symbol_map_pathmust point directly to the mapping file (absolute or relative path), not a directory.
Release notes
Open source →Features
- Add
sourceMaps.inject()for injecting debug IDs (#3088) - Add
--install-groupparameter tosentry-cli build uploadfor controlling update visibility between builds (#3094)
Fixes
- Upload Dart symbol mapping file (#347)
-
3.2.0-beta.114 Aug 2025 pre-releaseRelease notes
Open source →Features
- Upload Dart symbol mapping file (#347)
- Enables symbolication of Flutter issue titles for obfuscated builds.
- Supported: Android and iOS
- Not supported (yet): macOS, Linux and Windows.
- Generate the mapping file: Add
--extra-gen-snapshot-options=--save-obfuscation-map=<path>when building. Example:flutter build apk --obfuscate --split-debug-info=build/symbols --extra-gen-snapshot-options=--save-obfuscation-map=build/mapping.json - Add new field to Sentry Dart Plugin config:
dart_symbol_map_path: /path/to/build/mapping.json - Note: the path must point directly to the mapping file (absolute or relative path), not a directory.
# within your pubspec.yaml sentry # ... other Sentry config dart_symbol_map_path: /path/to/build/mapping.json
Release notes
Open source →Features
- Upload Dart symbol mapping file (#347)
- Enables symbolication of Flutter issue titles for obfuscated builds.
- Supported: Android and iOS
- Not supported (yet): macOS, Linux and Windows.
- Generate the mapping file: Add
--extra-gen-snapshot-options=--save-obfuscation-map=<path>when building. Example:flutter build apk --obfuscate --split-debug-info=build/symbols --extra-gen-snapshot-options=--save-obfuscation-map=build/mapping.json - Configure the plugin: Set
dart_symbol_map_path: build/mapping.json - Important:
dart_symbol_map_pathmust point directly to the mapping file (absolute or relative path), not a directory.
- Upload Dart symbol mapping file (#347)
-
3.1.115 Jul 2025 -
3.1.030 Jun 2025Release notes
Open source →Features
- Add release and dist to sourcemaps upload command (#333)
- This enables the uploaded bundle to be associated with the release for informational purposes
Fixes
- Should not exit program when web build path is not found (#337)
Release notes
Open source →Features
- Add release and dist to sourcemaps upload command (#333)
- This enables the uploaded bundle to be associated with the release for informational purposes
Fixes
- Should not exit program when web build path is not found (#337)
Release notes
Open source →New Features
- In the JavaScript API, added multi-project support to
releases.newDeploy()method. This method now accept aprojectsoption (array of project slugs), aligning them with the Rust CLI's multi-project capabilities and matching the existing behavior ofreleases.new()andreleases.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 newcommand 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 listcommand ignored the--projectoption (#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.
- Add release and dist to sourcemaps upload command (#333)
-
3.0.024 Jun 2025Release notes
Open source →Version 3.0.0 marks a major release of the Sentry Dart Plugin containing breaking changes for Flutter Web.
Breaking Changes
- Automatic Debug-ID Injection
- What’s new: By default, the plugin now embeds Debug IDs into your generated source maps.
- Why it matters: Debug IDs make symbolication of Flutter Web stack traces far more stable and reliable.
- Minimum Flutter SDK Requirement
- The Debug-ID feature only works with Sentry Flutter SDK 9.1.0 or newer.
- If you’re on 9.0.0 (or below), you won’t get Debug IDs automatically.
- Legacy Symbolication Mode
- If you cannot upgrade to Flutter SDK ≥ 9.1.0 yet, add this flag to your Sentry Dart Plugin config:
sentry: # ... other config legacy_web_symbolication: true
- This switches back to the “classic” source-map symbolication method you’ve been using.
Features
- Support injecting debug ids for Flutter Web (#319)
- Debug id loading will be the default symbolication in v3
- We have added the new field
legacy_web_symbolicationwhich you can set totrueif you want to keep using the old symbolication. It is set tofalseby default.
Enhancements
- Improve Flutter Web stacktraces by stripping verbose source prefixes (#320)
- This is only applied if you use the debug id symbolication which is enabled by default.
- This will not work with the legacy web symbolication.
Release notes
Open source →Version 3.0.0 marks a major release of the Sentry Dart Plugin containing breaking changes for Flutter Web.
Breaking Changes
- Automatic Debug-ID Injection
- What’s new: By default, the plugin now embeds Debug IDs into your generated source maps.
- Why it matters: Debug IDs make symbolication of Flutter Web stack traces far more stable and reliable.
- Minimum Flutter SDK Requirement
- The Debug-ID feature only works with Sentry Flutter SDK 9.1.0 or newer.
- If you’re on 9.0.0 (or below), you won’t get Debug IDs automatically.
- Legacy Symbolication Mode
- If you cannot upgrade to Flutter SDK ≥ 9.1.0 yet, add this flag to your Sentry Dart Plugin config:
sentry: dart_plugin: legacy_web_symbolication: true- This switches back to the “classic” source-map symbolication method you’ve been using.
- If you cannot upgrade to Flutter SDK ≥ 9.1.0 yet, add this flag to your Sentry Dart Plugin config:
Features
- Support injecting debug ids for Flutter Web (#319)
- Debug id loading will be the default symbolication in v3
- We have added the new field
legacy_web_symbolicationwhich you can set totrueif you want to keep using the old symbolication. It is set tofalseby default.
Enhancements
- Improve Flutter Web stacktraces by stripping verbose source prefixes (#320)
- This is only applied if you use the debug id symbolication which is enabled by default.
- This will not work with the legacy web symbolication.
Release notes
Open source →New Sentry Support Policy
sentry-cli3.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 ...andsentry-cli releases files ...subcommands (#2956). These commands provided functionality for managing release files, a feature that has been deprecated in Sentry. Users still usingsentry-cli files uploadto upload source maps should migrate tosentry-cli sourcemaps upload. - Removed the
sentry-cli sourcemaps explaincommand (#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-keyCLI flagSENTRY_API_KEYenvironment variableapi_keyconfiguration file fieldapiKeyoption in the JavaScript API
- Removed the
upload-proguardsubcommand's--app-id,--version,--version-code,--android-manifest, and--platformarguments (#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
--startedargument from thesentry-cli releases finalizecommand (#2972). This argument is a no-op, so any users using it should simply stop using it. - Removed the
--use-artifact-bundleflag fromsentry-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-clivia the npm package@sentry/cli:-
The
SentryCli.executemethod'sliveparameter now only takes boolean values (#2971). Settinglivetotruenow 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
optionparameter toReleases.uploadSourceMapsno longer takes aliveproperty (#2971). We now always execute the command withliveset totrue. -
Removed the
apiKeyoption fromSentryCliOptions(#2935). If you are usingapiKey, you need to generate and use an Auth Token via theauthTokenoption, instead. -
Removed the
useArtifactBundleoption fromSentryCliUploadSourceMapsOptions(#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
SentryCliReleaseshas 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('@sentry/cli'); // New (named import) const { SentryCli } = require('@sentry/cli');For ESM imports:
// Old import SentryCli from '@sentry/cli'; // New import { SentryCli } from '@sentry/cli';
Improvements
- The
sentry-cli upload-proguardcommand now uses chunked uploading by default (#2918). Users who previously set theSENTRY_EXPERIMENTAL_PROGUARD_CHUNK_UPLOADenvironment 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
debugIdfield, per the TC39 Debug ID proposal (#3005). This change affects thesentry-cli sourcemaps injectcommand and, unless--no-rewriteis passed, thesentry-cli sourcemaps uploadcommand. Sentry CLI can still read thedebug_idfield, but whenever the CLI writes or rewrites a source map, we always usedebugId. - The
sentry-cli build uploadcommand now automatically tracks Sentry plugin versions from theSENTRY_PIPELINEenvironment variable (#2994). WhenSENTRY_PIPELINEcontains a recognized Sentry plugin (e.g.,sentry-gradle-plugin/4.12.0orsentry-fastlane-plugin/1.2.3), the plugin version is written to the.sentry-cli-metadata.txtfile 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).
- Automatic Debug-ID Injection
-
2.4.121 Feb 2025Release notes
Open source →Various fixes & improvements
- ref: Print better error when processing appcenter paths (#1287) by @kamilogorek
- fix: Make sure release exists before querying for artifacts (#1284) by @kamilogorek
-
2.4.027 Jan 2025Release notes
Open source →Release notes
Open source →Release notes
Open source →Various fixes & improvements
- ci: Disable rustup self-update (#1278) by @kamilogorek
- feat: Add decompress flag to sourcemaps and files upload (#1277) by @kamilogorek
- feat: Use checksum to dedupe uploaded release artifacts (#1275) by @kamilogorek
-
2.3.017 Jan 2025Release notes
Open source →Various fixes & improvements
- fix: Allow for using --auth-token with login command (#1266) by @kamilogorek
- deps: Update all Rust dependencies (#1265) by @kamilogorek
- fix: Increase TempFile robustness on Windows (#1256) (#1263) by @kamilogorek
- ref: Remove confusing ending dots from command logs (#1261) by @kamilogorek
- fix: Correct typo in sourcemaps explain output (#1258) by @huwq1987
- fix: Use first frame that has context-line in explain (#1255) by @kamilogorek
- feat: Add send-envelope command (#1254) by @kamilogorek
-
2.2.102 Dec 2024 -
2.2.018 Nov 2024Release notes
Open source →Changes
- Upload debug symbols for known release build paths and the configured
symbols_path(#277) Previously, all debug symbols recognized by Sentry CLI were uploaded (starting in the current directory by default). Now, the plugin checks the paths whereflutter buildoutputs debug symbols for release builds and only uploads those.
Features
- Add urlPrefix to sentry configuration (#253)
Fixes
- Only upload
.dartfiles withupload-sourcemapswhenupload_sourcesis enabled (#247)- Enable
upload_sourcesto opt in to Flutter web source context
- Enable
Dependencies
Release notes
Open source →Various fixes & improvements
- feat: Compute and upload il2cpp line mappings (#1248) by @loewenheim
- ref: Skip protected zip files when uploading debug files (#1245) by @kamilogorek
- Upload debug symbols for known release build paths and the configured
-
2.1.018 Jun 2024Release notes
Open source →Features
- Add support for build files folder parameter (#235)
- Support SENTRYCLI_CDNURL env (#230)
- Add
sentry_cli_versionparameter (#243)
Fixes
- Revert sentry-cli to v2.27.0 (#241)
Release notes
Open source →Source Maps Upload Check "y-tho" (ongoing)
Problem statement:
Uploading source maps is a common source of frustration. Source maps are also one of the great value adds to our in product experience. We want to automate supporting customers with frequent issues.
https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/
_Outcome: _
Developers will be provided with a tool to help them discover any issues they may have when uploading source maps
Sentry support will have a tool and docs to suggest to customers to hopefully first discover issues, and second at least know what their problem is NOT.
Key measurements:
- qualitative: Is this useful for customers and support
- quantitative: Can we try to influence the number of Zendesk tickets
- quantitative: Can we influence the resolution time of source maps related Zendesk tickets
Can we find a way to track in zendesk the number of times the sentry-cli “y-tho“ functionality was useful
Additional
This is something users would run locally so I do not think we can track usage exactly what was not covered in y-tho
- Verify your source maps are built correctly
- Verify your source maps work locally
- Verify your source files are not too large
- this is a fuzzy requirement today in sentry
- Verify artifacts are not gzipped
- Verify workers are sharing the same volume as web (if running self-hosted Sentry via Docker)
- Should spit out an easily readable and easily copy and paste - to put into ZenDesk or elsewhere for support colleagues
Possible second milestone:
https://github.com/getsentry/rust-sourcemap/tree/master/cli
- In sentry error incorrect source map location
- this helps when producing sourcemaps locally then line and column
- this verify that it resolves locally
- if yes then it is a problem in between on sentry server side or upload
- 1st Verifies what you upload to sentry is exactly what you upload to sentry
- 2nd step from “y-tho” ensure previous steps are not for waste
- What is being automated?
- on release page you have your files (release artificats)
- download
- manually check the line number matches the error
- if correct then data is correct
- then you know an error with cli and not with the source maps that were uploaded
- on release page you have your files (release artificats)
By: @kamilogorek (#1235)
Various fixes & improvements
- ref: Change comment format for find_matching_artifact (#1243) by @kamilogorek
- ref: Log correct AppCenter error message (#1243) by @kamilogorek
- fix: Respect no-zips option for debug files upload (#1239) by @saf-e
- chore: fix recommended VS Code extension name (#1240) by @vaind
- ref: Rename VERSION to SENTRY_CLI_VERSION in install readme (#1227) by @kamilogorek
- feat: Add organizations list command (#1213) by @kamilogorek
- docs(cli): Sync get-cli readme with our docs; add version specifier (#1225) by @kamilogorek
- test: Add integration tests for projects command (#1212) by @kamilogorek
- fix: replace git.io links with redirect targets (#1209) by @asottile-sentry
-
2.0.017 Apr 2024Release notes
Open source →Breaking Changes
- Update env/config
releaseanddistbehaviour (#217)- Default release: automatically constructs the release identifier from pubspec.yaml using the format:
name@version. If a build number is included in the version, it is utilized as dist. - Custom release can be specified via an environment variable or plugin configuration. Once set, it is used as is without further modification.
- Custom dist can also be set via environment variables or plugin configuration. It replaces or adds to the build number in the default release.
- Environment variables:
SENTRY_RELEASEandSENTRY_DISTenvironment variables take precedence over plugin config values.
- Default release: automatically constructs the release identifier from pubspec.yaml using the format:
Features
- Custom
distoverrides version build number (#216)- For instance, if the initial release version is
[email protected]+1, specifying a custom dist value of 2 will update the version to[email protected]+2.
- For instance, if the initial release version is
- Add option to provide alternative binary directory (#214)
- Support configuration arguments via
--sentry-define(#198) - Provide path to local
sentry-cli(#224)
Dependencies
Release notes
Open source →This is the first, long-overdue major release in over 5 years of sentry-cli's life. Some APIs were removed, some reworked, some newly added.
Most of introduced API changes are backward compatible through hidden aliases, so there is no immediate need for users developing 3rd party tools to make all the changes immediatelly. We do however encourage everyone to do it sooner or later, as deprecated items will be removed in the next major releases.
Breaking changes are denotated with (breaking) tag, and appropriate required changes are provided for each entry.
New APIs
- feat: Add
debug-filescommand, which is a joined functionality ofdifutilandupload-difcommands. - feat: Add
deployscommand, which was extracted fromreleases deployssubcommand. - feat: Add
filescommand, which was extracted fromreleases filessubcommand. - feat: Add
sourcemaps uploadcommand, which was extracted fromreleases files upload-sourcemapssubcommand. - feat: Add
sourcemaps resolvecommand. - feat: Allow for specifying global
--headerargument, which supports multiple occurences, to configure outgoing requests - feat: Implement global
--quiet/--silentflags to allow silencingstdoutoutput (This flag is currently implemented only for selected subcommands)
Removed APIs
- ref: Remove
react-native codepushsubcommand (usereact-native appcenterinstead) (breaking) - ref: Remove
react-native-gradleandreact-native-xcodecommands (usereact-native gradleandreact-native xcodeinstead) (breaking) - ref: Remove
crash_reportingrelated code andwith_crash_reportingcrate feature (no required changes) (breaking) - ref: Remove
SENTRY_NO_PROGRESS_BARenv var in favor ofSENTRYCLI_NO_PROGRESS_BAR(rename env variable) ( breaking) - ref: Hide
difutil idsubcommand (usedebug-files checkinstead) - ref: Hide
upload-dsymcommand (usedebug-files uploadinstead) - ref: Make
releases upload-sourcemaps --rewritea default behavior now - ~ref: Remove
upload-dsymcommand (usedebug-files uploadinstead) (breaking)~ restored in 2.0.2 as hidden alias - ~ref: Remove
difutil idsubcommand (usedebug-files checkinstead) (breaking)~ restored in 2.0.2 as hidden alias - ~ref: Remove
monitorscommand (support for this feature has been dropped) (breaking)~ - restored in 2.0.3 as hidden command - ~ref: Remove
bash-hookcommand (use1.xif you still need the functionality) (breaking)~ - restored in 2.0.3 as hidden command
Breaking Changes
- ref: Update minimal required
nodeversion tov12(update node version) (breaking) - ref: Rename
--headerargument ofreleases files uploadcommand to--file-header(rename flag) (breaking) - ref: Rename
CUSTOM_HEADERtoSENTRY_HEADERanddefaults.custom_headertohttp.header(rename env variable or update config file) (breaking) - ref: Make
ignore-emptyforreleases set-commitsa default behavior and hide--ignore-emptyflag (remove--ignore-emptyusage) (breaking)
Various fixes & improvements
- feat: Implement
--quietflag forreleases upload-sourcemapscommand - feat: Implement
--quietflag fordifutil checkcommand - ref: Make
--auth-tokena global argument - ref: Make all
ProgressBarinstances and logs always write tostderr - ref: Migrate error handling from
failuretoanyhowcrate
- Update env/config
-
1.7.116 Feb 2024Release notes
Open source →Fixes
- Updated the
processdependency range to>=4.2.4 <6.0.0(#202).- This update resolves a version conflict issue when using the
integration_testpackage with Flutter version3.19.0
- This update resolves a version conflict issue when using the
- Updated the
-
1.7.005 Feb 2024Release notes
Open source →Release notes
Open source →- Sourcemap uploads now automatically replace previous files with the same name.
- Honor
CLICOLORenvironment variable - Added progress bars for source map and debug symbol upload
- No longer attempt to upload multiple versions of debug symbols with the same UUID. This was an issue where signed and unsigned debug symbols were discovered in derived data in case of debug builds.
- Support
--validateand--rewritein one command better for source map upload.
-
1.6.308 Nov 2023Release notes
Open source → -
1.6.226 Sep 2023 -
1.6.007 Sep 2023Release notes
Open source →- Added
--fingerprintsupport tosend-event - Added distribution support.
Breaking Change: releases managed for react-native and mobile are now using the new distribution feature. Use older versions of
sentry-cliif you do not wish to manage distributions on self hosted Sentry versions. - Added
-
1.5.020 Jul 2023Release notes
Open source →Release notes
Open source →- Added
--uuidparameter toupload-dsym - Added
--no-zipsparameter toupload-dsym - Added
--derived-dataparameter toupload-dsym
- Added
-
1.4.019 Jun 2023Release notes
Open source →Release notes
Open source →- Added basic support for working with the improved relases API that span projects in an org
- Added deploy support
-
1.3.024 May 2023Release notes
Open source →Release notes
Open source →- improved file and release list rendering
- added
sentry-cli releases propose-version
-
1.2.008 May 2023Release notes
Open source →Release notes
Open source →- Resolved references to sourcemaps sometimes being incorrectly detected
- Resolved an issue where an incorrect Info.plist file was found (#48)
- Added support for
.envfiles - Better support SSL CA bundles on linux systems (probe more locations)
- Added
--finalizeoption to automatically finalize releases on creation - Improved
sentry-cli infocommand rendering and clarity - Added background processing for
sentry react-native-xcode
-
1.1.002 Mar 2023Release notes
Open source →upload-dsymswhen launched from xcode will now upload symbols in the background and notify with OS X notifications about changes
-
1.0.027 Feb 2023Release notes
Open source →- Added support for associating dsyms with builds on supporting sentry servers
-
1.0.0-beta.516 Jan 2023 pre-release -
1.0.0-beta.414 Oct 2022 pre-release -
1.0.0-beta.312 Oct 2022 pre-release -
1.0.0-beta.229 Mar 2022 pre-release -
1.0.0-beta.105 Nov 2021 pre-release -
1.0.0-alpha.412 Oct 2021 pre-release -
1.0.0-alpha.301 Oct 2021 pre-releaseRelease notes
Open source →Dependencies
- Bump sentry-cli 1.69.1 which includes a fix for Dart debug symbols (#8)
-
1.0.0-alpha.225 Aug 2021 pre-release -
1.0.0-alpha.120 Aug 2021 pre-release -
1.0.0-RC.101 Feb 2023 pre-release