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.0.1" 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.0.1)Integrity Checksum
sentry-cli-Darwin-arm64sha384-bf6f18200b98f0a79bfbcff8b6b9a01b6960f52befb024616cb211f326f8ce23
sentry-cli-Darwin-universalsha384-720af732451032b5be7df75baacc313ea21ee645f9ad4872d0a39524db274981
sentry-cli-Darwin-x86_64sha384-b641eb37c84993fbc4ef21b4bed499967c711035ecb85421f3ce9abe635b2499
sentry-cli-Linux-aarch64sha384-5eaa180ae11e63af80cab6303a8d223dddb7dcea7c0a7c933b26fa91b54c9cf6
sentry-cli-Linux-armv7sha384-3dc9cb18e302db1bd1c7c6edb2cdbe0fe250ab4b815787f551a07553b692e42b
sentry-cli-Linux-i686sha384-c6214a8f34b39e572d5e9dbebe118d26e4707ceced807439bfb845b6b8373c29
sentry-cli-Linux-x86_64sha384-7cf53a2089fd5a6a9a0c2eb972d62c9c8eefea19dcdd5dd58604aa8bc4212538
sentry-cli-Windows-aarch64.exesha384-d57556d2e1cb4f52af367c1f23101dc30963e080c99cf670aec87001533265ed
sentry-cli-Windows-i686.exesha384-e691b753e7477bc7ec72cd7b8149e34ef52754cbbcb774823c885576215f4683
sentry-cli-Windows-x86_64.exesha384-a85b00f651ae73c345a75788378f31b210226193d54e421fe2d3974392af591b
sentry_cli-3.0.1-py3-none-macosx_10_15_x86_64.whlsha384-86893f23d034a6bd3ba10b8dc324ec4579e5fd57adbc5968de3c86b18c1fb562
sentry_cli-3.0.1-py3-none-macosx_11_0_arm64.whlsha384-db1e060ad5f0673c4e7db510fca2aa4dc1d57d2829b424c575912cd59d5e6051
sentry_cli-3.0.1-py3-none-macosx_11_0_universal2.whlsha384-027f3e605f178666d296188317754cfec20cd9d6cb70c780011ac8827c7a30d5
sentry_cli-3.0.1-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_2_aarch64.whlsha384-caa79f434fee12ac9c36aea3ab8a54691140a604bc88e854aac6d031f3dc5208
sentry_cli-3.0.1-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_2_armv7l.whlsha384-409b3db4f53b64dae777ae8e148bc2a14d7f001706c457c2d2ec25ea62d2c0e1
sentry_cli-3.0.1-py3-none-manylinux_2_17_i686.manylinux2014_i686.musllinux_1_2_i686.whlsha384-836853467b2e7a2a402b89881136ca1c986967446f32be1c84aee1fc5e6dc15c
sentry_cli-3.0.1-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.musllinux_1_2_x86_64.whlsha384-1b1192faa00339aae9c0ea99eccc91ac897019c13a3171dd189051bcd03d90f3
sentry_cli-3.0.1-py3-none-win32.whlsha384-40673cd08f463f6e5c13ab2ed3ce65496669ec9d2da679a5111716e9145b78ef
sentry_cli-3.0.1-py3-none-win_amd64.whlsha384-bd042f18c38c239aa51b83d77c22c92ec30061bd834932afda5affb3dec64226
sentry_cli-3.0.1-py3-none-win_arm64.whlsha384-45d9913c12bb88a0e6da51e097fd5e7bc138a4fa7ae9c8bc8c60dbfe59a77607
sentry_cli-3.0.1.tar.gzsha384-2f04bcafc7dee8a75ac5ac76d87fa8c0de021e5d9b528b57314237d386e0bb1e

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