Installation

Learn about the different methods available to install `sentry-cli`.

Depending on your platform, there are different methods available to install sentry-cli.

You can find the list of releases on the GitHub release page. We provide executables for Linux, OS X and Windows. It’s a single file download and upon receiving the file you can rename it to just sentry-cli or sentry-cli.exe to use it.

If you are on macOS or Linux, you can use the automated downloader which will fetch the latest release version for you and install it:

Copied
curl -sL https://sentry.io/get-cli/ | sh

We do however, encourage you to pin the specific version of the CLI, so your builds are always reproducible. To do that, you can use the exact same method, with an additional version specifier:

Copied
curl -sL https://sentry.io/get-cli/ | SENTRY_CLI_VERSION="3.8.0" sh

This will automatically download the correct version of sentry-cli for your operating system and install it. If necessary, it will prompt for your admin password for sudo. For a different installation location or for systems without sudo (like Windows), you can export INSTALL_DIR=/custom/installation/path before running this command.

To verify it's installed correctly you can bring up the help:

Copied
sentry-cli --help

There is also the option to install sentry-cli via npm for specialized use cases. This, for instance, is useful for build servers. The package is called @sentry/cli and in the post installation it will download the appropriate release binary:

Copied
npm install @sentry/cli

You can then find it in the .bin folder:

Copied
./node_modules/.bin/sentry-cli --help

In case you want to install this with npm system wide with sudo you will need to pass --unsafe-perm to it:

Copied
sudo npm install -g @sentry/cli --unsafe-perm

By default, this package will download sentry-cli from the CDN managed by Fastly. To use a custom CDN, set the npm config property sentrycli_cdnurl. The downloader will append "/<version>/sentry-cli-<dist>".

Copied
npm install @sentry/cli --sentrycli_cdnurl=https://mymirror.local/path

Or add property into your .npmrc file (https://docs.npmjs.com/files/npmrc)

Copied
sentrycli_cdnurl=https://mymirror.local/path

Another option is to use the environment variable SENTRYCLI_CDNURL.

Copied
SENTRYCLI_CDNURL=https://mymirror.local/path npm install @sentry/cli

Options listed below control how sentry-cli install script behaves, when installed through npm.

SENTRYCLI_CDNURL:

If set, the script will use given URL for fetching the binary. Defaults to https://downloads.sentry-cdn.com/sentry-cli.

SENTRYCLI_USE_LOCAL:

If set to 1, sentry-cli binary will be discovered from your $PATH and copied locally instead of being downloaded from external servers. It will still verify the version number, which has to match.

SENTRYCLI_SKIP_DOWNLOAD:

If set to 1, the script will skip downloading the binary completely.

SENTRYCLI_SKIP_CHECKSUM_VALIDATION:

If set to 1, the script will skip the checksum validation phase. You can manually verify the checksums by visiting Build Checksums page.

SENTRYCLI_NO_PROGRESS_BAR:

If set to 1, the script will not display download progress bars. This is a default behavior for CI environments.

SENTRYCLI_LOG_STREAM:

If set, the script will change where it writes its output. Possible values are stdout and stderr. Defaults to stdout.

If you are on OS X, you can install sentry-cli via homebrew:

Copied
brew install getsentry/tools/sentry-cli

If you are on Windows, you can install sentry-cli via Scoop:

Copied
> scoop install sentry-cli

For unsupported distributions and CI systems, we offer a Docker image that comes with sentry-cli preinstalled. It is recommended to use the latest tag, but you can also pin to a specific version. By default, the command runs inside the /work directory. Mount relevant project folders and build outputs there to allow sentry-cli to scan for resources:

Copied
docker pull getsentry/sentry-cli
docker run --rm -v $(pwd):/work getsentry/sentry-cli --help

You can use sentry-cli update and sentry-cli uninstall to update or uninstall the sentry-cli binary. These commands may be unavailable in certain situations, generally when sentry-cli has been installed by a tool like homebrew or yarn, either directly or as a dependency of another package. In those cases, the same tool will need to be used for updating and removal. If you find that sentry-cli update and sentry-cli uninstall aren't working and you don't know how the package was installed, running which sentry-cli will often provide a clue as to which tool to use.

When downloading an executable from a remote server, it's often a good practice to verify, that what has been downloaded, is in fact what we expect it to be. To make sure that this is the case, we can use checksum validation. A checksum is the value calculated from the contents of a file, in a form of hash, in our case SHA256, and it acts as the data integrity check, as it's always producing the same output, for a given input.

Below is the table of SHA256 checksums for all available build targets that our CLI supports. To calculate the hash of a downloaded file, you can use sha256sum utility, which is preinstalled in OSX and most Linux distributions.

Filename (v3.8.0)Integrity Checksum
sentry-cli-Darwin-arm64sha384-1dda212b0e168b9c4dc48d7d3aa24c1c37de9c6edf786e6ae661236e529969cd
sentry-cli-Darwin-universalsha384-2c26914636c47ab9bf9e710484ad7b44d371cbec8bd29cafb36b3cf877bf4285
sentry-cli-Darwin-x86_64sha384-279c795b15de7a76106d30b6611b7942b1a97323307327bafc18335f10384c4d
sentry-cli-Linux-aarch64sha384-eaea24b5b47b61a96d9a2e353268ea41fd9a8c5b7979694330df614d4af672bf
sentry-cli-Linux-armv7sha384-f5cf9d6b3101f740f2d60c371c0a76330cb5072206216641edce72353e8cf503
sentry-cli-Linux-i686sha384-ecbbc8e9b8050831cc1196edfc8df6d72660c4fdc7d844722ab6bc2a3a778173
sentry-cli-Linux-x86_64sha384-13f8cb34ae01a6a272d7d7c22e277a105286615b4020de900ea95a8de47cdbb6
sentry-cli-Windows-aarch64.exesha384-174786337bf2d3cd3386c14aab122ba3d3bbd49b98e124666b03f63f54e4104f
sentry-cli-Windows-i686.exesha384-f10b90a1e62a81a5184a076ac097c6a31a56a0b493648d066948adb0691d6370
sentry-cli-Windows-x86_64.exesha384-2257cf6805a616f5c3ee291a549ebbba021190048b646adc006beb4e8cdef7fd
sentry_cli-3.8.0-py3-none-macosx_10_15_x86_64.whlsha384-a189d9f29e224269b1183a6717727d5d3022f8ae8e4d07add4722d7120ce7140
sentry_cli-3.8.0-py3-none-macosx_11_0_arm64.whlsha384-51aa27ef49081e56b8da50e4ff6420bce53af6ed914c5cb90929255c9f2e71ac
sentry_cli-3.8.0-py3-none-macosx_11_0_universal2.whlsha384-275f9141cb3ac8fa0041b57c06a96983c1ec1a838717c90472add9e6ef0111fa
sentry_cli-3.8.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_2_aarch64.whlsha384-3cf62b1fa957fe75579cb932a94a831bcee3ace9d4c7601148b16fc718408b0e
sentry_cli-3.8.0-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_2_armv7l.whlsha384-6e1de5aaa2ce1e417840fa27dab3ee66fd19439c763f557a528445f4360b4a2e
sentry_cli-3.8.0-py3-none-manylinux_2_17_i686.manylinux2014_i686.musllinux_1_2_i686.whlsha384-e4b6f175eb68b639c0536038733a6f767cc030d158ec6b76b2d4be08f1d9e55b
sentry_cli-3.8.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.musllinux_1_2_x86_64.whlsha384-9881d84e8a253fa2350ec82a70d14d6bf62e209289e532927746fd438d471e40
sentry_cli-3.8.0-py3-none-win32.whlsha384-c425e144d253bcccc1cbaf7b3267058ac9e41decdc0a5981f27eff0f0c627acb
sentry_cli-3.8.0-py3-none-win_amd64.whlsha384-10556ba78d255375fbecfacab46e5a4b60ac629a35f1df88e436fad8e9e91b1b
sentry_cli-3.8.0-py3-none-win_arm64.whlsha384-1c67ad4b879606c057ea7f46c296753cd62e4acdf58e4730f160df310af5267f
sentry_cli-3.8.0.tar.gzsha384-cf9e4d68080dbdd8c3ba8d541f2097bb9648ab56b7abde8b5681461b4a40e4f7

If you would like to verify checksums for historic versions of the sentry-cli, please refer to our release registry directly, which can be found at https://release-registry.services.sentry.io/apps/sentry-cli/{version}. For example, https://release-registry.services.sentry.io/apps/sentry-cli/1.74.4.

Was this helpful?
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").