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="2.58.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 (v2.58.0)Integrity Checksum
sentry-cli-Darwin-arm64sha384-acbbb58f078a465e9016639c0ac25dce4b2443ebe9b9f1c027938557eba6bb5e
sentry-cli-Darwin-universalsha384-b23b628f2d000898cbc8b323339218134e0856b0dfa2491c0328c09a27b02e69
sentry-cli-Darwin-x86_64sha384-a105b14eae786d1db9ef7e716f92d83e97f54849a4cc18a7864f5eb45143e3c8
sentry-cli-Linux-aarch64sha384-4ee4e5341ae3366a5e629ab7bebe3465f1443e7acc5daa6e808ce2ded0a412ba
sentry-cli-Linux-armv7sha384-be88fa9943072618f1c3ca785f447a2c1c6dbd800897ad64405bf91bd1af254c
sentry-cli-Linux-i686sha384-cee64604f94c401d3e215dfcb3f5c6292a6ff3df90c3c98d155cbb1da7ed0bc1
sentry-cli-Linux-x86_64sha384-735b266c50b44735167292fef65c5889737f3a4d9f8150937e6d454217ca741d
sentry-cli-Windows-aarch64.exesha384-08413d9fc93e63a94e5af9a6c8884a56c67ddc2b01b4c5169f8d682f6203c2c4
sentry-cli-Windows-i686.exesha384-90c431804200c4bb600dd94667c0bd33bd33e486185cce3d168d65f74c2e2f02
sentry-cli-Windows-x86_64.exesha384-3f7e7d8ab53052fb6d41f3428df405b5cc521474d26d4bfd3fb6b05cd2e708c9
sentry_cli-2.58.0-py3-none-macosx_10_15_x86_64.whlsha384-427147bbd7001a63fafc6625ec2a855491313883467fa0b8e6753d37a7bc0d1e
sentry_cli-2.58.0-py3-none-macosx_11_0_arm64.whlsha384-51b1de2466882795878031e9c28b05f614eacfa9315112ce4ef7e41212f0be93
sentry_cli-2.58.0-py3-none-macosx_11_0_universal2.whlsha384-f0a5e692ac51d2196ac648a814902a828d37ef69c32071d700e55d76c7c303d7
sentry_cli-2.58.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_2_aarch64.whlsha384-6bb4f41cd63513b0aaa4015a611f1e17a8f357f2ceee4a9e3c1aa6caca97a2c8
sentry_cli-2.58.0-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_2_armv7l.whlsha384-05140fcb6f6c444bc70302ea790a16d197e443748e5f868c412abc7933624ee2
sentry_cli-2.58.0-py3-none-manylinux_2_17_i686.manylinux2014_i686.musllinux_1_2_i686.whlsha384-be4e36855d6f9af20b0065dc0360d4a8867d0eca10b5ed70e17b93a5e31ca299
sentry_cli-2.58.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.musllinux_1_2_x86_64.whlsha384-88d800b8069190999d8a020a1bb3d1030d189a3695664f5dc31934b811de276a
sentry_cli-2.58.0-py3-none-win32.whlsha384-4c99ba765ef58fdc2d8043cbdcb197444701b9518c99adb48be5406ceb151933
sentry_cli-2.58.0-py3-none-win_amd64.whlsha384-bcf918943326e57715d828360a9c896f6057c1d1e85c2754817de3a2634bc036
sentry_cli-2.58.0-py3-none-win_arm64.whlsha384-0af071c2f5e6101f66c6fc16307c5fe7c5b470ec9534b12123491c57259d2e80
sentry_cli-2.58.0.tar.gzsha384-18e5e2294c5e6e62bf8a6bcc15604e70ac9148182a9d621712cd5d25363b5ce0

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").