From ba54367a8cf08e69e6c8e6a664d3a3e80f955b63 Mon Sep 17 00:00:00 2001 From: Daniel Szoke Date: Wed, 12 Nov 2025 11:15:06 +0100 Subject: [PATCH] docs(sourcemaps): Remove mentions of `sentry-cli sourcemaps explain` `sentry-cli sourcemaps explain` has been deprecated for some time, and is scheduled for removal (https://github.com/getsentry/sentry-cli/issues/2865, [CLI-195](https://linear.app/getsentry/issue/CLI-195/remove-sentry-cli-sourcemaps-explain-command)). So, we should remove all mentions of the command from the docs, and point users to alternative debugging steps, instead. Resolves #15471 Resolves [DOCS-2346](https://linear.app/getsentry/issue/DOCS-2346/remove-mentions-of-sentry-cli-sourcemaps-explain-from-the-docs) --- .../legacy-troubleshooting/javascript.mdx | 19 +------------- .../legacy-uploading-methods/javascript.mdx | 25 ------------------- .../sourcemaps/troubleshooting/javascript.mdx | 22 ++-------------- 3 files changed, 3 insertions(+), 63 deletions(-) diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx index 09f457ea2ecc6..cb6da7d5b4f7f 100644 --- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx @@ -1,21 +1,4 @@ -Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps set up, you can either: - -1. Use our automated verification tool inside `sentry-cli`, or -2. Follow the manual steps listed below - -## Use the Sentry CLI - -To use the automated verification process, install and configure the Sentry [Command Line Interface](/cli/). Then, use the `sourcemaps explain` command, calling it with the relevant event ID, found in the top-left corner of the **Issue Details** page in [sentry.io](https://sentry.io). - -For example, "Event ID: c2ad049f": - -![Image highlighting where to find the ID of an event on Sentry](./img/event_id.png) - -```shell -sentry-cli sourcemaps explain c2ad049fd9e448ada7849df94575e019 -``` - -The CLI output should give you useful information about what went wrong with your source maps setup. +Setting up source maps can be tricky, but it's worth it to get it right. You can follow the steps below to troubleshoot your source maps set up. diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx index 9abc0c011f89e..3bb4a7e0803e4 100644 --- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx @@ -267,31 +267,6 @@ Sentry.init({ If you followed all of the steps above but still have issues setting up source maps using the legacy method this section will try to help troubleshoot your setup. -To troubleshoot your source maps set up, you can either: - -1. Use our automated verification tool inside `sentry-cli`, or -2. Follow the manual steps listed below - -### Use the Sentry CLI - -To use the automated verification process, install and configure the Sentry [Command Line Interface](/cli/). Then, use the `sourcemaps explain` command, calling it with the relevant event ID, found in the top-left corner of the **Issue Details** page in [sentry.io](https://sentry.io). - - - -The `sourcemaps explain` command requires an auth token with the following scopes: `project:admin`, `release:admin`, `event:read`, and `organization:read`. We recommend creating an [internal integration token](/organization/integrations/integration-platform/internal-integration/) over a personal token. - - - -For example, "Event ID: c2ad049f": - -![Image highlighting where to find the ID of an event on Sentry](./img/event_id.png) - -```shell -sentry-cli sourcemaps explain c2ad049fd9e448ada7849df94575e019 -``` - -The CLI output should give you useful information about what went wrong with your source maps setup. - ### Verify a release is configured in your SDK diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index bf57f4ba6ac51..b0acaecd493ec 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -30,27 +30,9 @@ Dependency versions that require the legacy method of uploading source maps incl -Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps set up, you can either: +Setting up source maps can be tricky, but it's worth it to get it right. You can follow the steps below to troubleshoot your source maps set up. -1. Use our automated verification tool inside `sentry-cli`, or -2. Follow the manual steps listed below - -## Use the CLI - -To use the automated verification process, install and configure the Sentry [Command Line Interface](/cli/). Then, use the `sourcemaps explain` command, calling it with the relevant event ID, found in the top-left corner of the **Issue Details** page in [sentry.io](https://sentry.io). - -For example, "Event ID: c2ad049f": - -![Image highlighting where to find the ID of an event on Sentry](./img/event_id.png) - -```shell -sentry-cli sourcemaps explain c2ad049fd9e448ada7849df94575e019 -``` - -The CLI output should give you useful information about what went wrong with your source maps setup. -If it doesn't, let us know by filing an issue on our [Sentry CLI repo](https://github.com/getsentry/sentry-cli) so we can make it better. - -## Follow Manual Steps +## Troubleshooting Steps ### Verify Artifacts Are Uploaded