Update docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids/index.mdx

Co-authored-by: Luca Forstner <[email protected]>

Author: priscilawebdev

docs/platforms/javascript/common/sourcemaps/troubleshooting_js/debug-ids/index.mdx

@@ -29,7 +29,7 @@ Inspired by approaches in native language ecosystems, Debug IDs are globally uni
 
 When using sentry-cli or Sentry plugins for Webpack, Vite, or Rollup, Debug IDs are deterministically generated based on the source file contents. Note that deterministic Debug IDs for esbuild are not currently supported.
 
-This approach is Sentry's recommended and most reliable method for associating minified JavaScript files with their original source code, making it easier to trace errors back to their source. As a result, **creating a release is no longer required**.
+This approach is Sentry's recommended and most reliable method for associating minified JavaScript files with their original source code, making it easier to trace errors back to their source. Because debug IDs will generally change across releasess if the file content is changed **creating a release is no longer required**. Release names were previously used to disambiguate sourcemaps with the same name across deployments.
 
 <Alert>