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.5.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.5.0)Integrity Checksum
sentry-cli-Darwin-arm64sha384-07c2144befbbe0cf8e4285c2751ba3818a55ced6ebd51d0268380e5e30ce9aed
sentry-cli-Darwin-universalsha384-46a439a75a8dda4719dbfded7b09388dc4b2aa7e1976e28102dfeb14401b8587
sentry-cli-Darwin-x86_64sha384-beae514b7d117cb248accbabc87ae9003c0a3795811b28e0640c15e654a78747
sentry-cli-Linux-aarch64sha384-94c758dee171ba4f248c0514806c1a03331a59a59582874500f17555b922b257
sentry-cli-Linux-armv7sha384-bc036c910ab997ee92e519bd3aa8052ecf432298bf7eb0325d2f82fc9beae016
sentry-cli-Linux-i686sha384-8d860d698c40e86a269204c77893a2fecb5467c5dc7b1de56e0877313aa245eb
sentry-cli-Linux-x86_64sha384-522d469086996996322052b8f46bb679f010c53d884521023e79aa7680627104
sentry-cli-Windows-aarch64.exesha384-02be1110a4aca28ab0e0aceb41bb1440148748888d79f5024fe66a160872bd18
sentry-cli-Windows-i686.exesha384-c03f3ddc68bfae1795ed817b102250642dd06ca0e42339e594454e3a9a42ef93
sentry-cli-Windows-x86_64.exesha384-7b7db2a8650644a77beef525e1464db3dad0b5313f6589f2991d39af7eda78aa
sentry_cli-3.5.0-py3-none-macosx_10_15_x86_64.whlsha384-b3f915800dc28dbc7b0772047fe6228c0359445022a57ad0017b3dba40ce4db0
sentry_cli-3.5.0-py3-none-macosx_11_0_arm64.whlsha384-be486dd34adfae3ef2b7c8c8cff7f59071752f058468b20d5639f49611e7715f
sentry_cli-3.5.0-py3-none-macosx_11_0_universal2.whlsha384-3e270b97ec7b6394e6e09c72d3e87e1c0b656503d736236e11c49cb548d35a94
sentry_cli-3.5.0-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_2_aarch64.whlsha384-bb488adc6a1532dc69d03754a2e8dd337c6221d1251b5f01328e03d349828e97
sentry_cli-3.5.0-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_2_armv7l.whlsha384-bb198f20e23c47d0f5ebcc1c5f1a9c9ba856710c9fd03de09a515f077797b2d2
sentry_cli-3.5.0-py3-none-manylinux_2_17_i686.manylinux2014_i686.musllinux_1_2_i686.whlsha384-0bc23d2e607460eea96369d40f66dab244463b0efd583e21925c101ccd760fc0
sentry_cli-3.5.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.musllinux_1_2_x86_64.whlsha384-20f2ed4938293a0f239d5db771ccc133d159bd41edb9e5004528a440dc7181c1
sentry_cli-3.5.0-py3-none-win32.whlsha384-2e6cb9248db347e2e4853a1a81c24c4c7ca829deeff0af44a690799b034517bc
sentry_cli-3.5.0-py3-none-win_amd64.whlsha384-32e8a10177d6953b75bf37b1d069b9023d3f1ffebdc7c4c120b8b458eaec186a
sentry_cli-3.5.0-py3-none-win_arm64.whlsha384-0b7a27599658b4dbd319b136340f83a757b55a38fc7c41ab0e13d85b8116ceae
sentry_cli-3.5.0.tar.gzsha384-58ffa7bdf923484d8fa359213868596ebcf6202b516fa8f53abee0f303a4a4ec

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