Upload and verify JS/TS sourcemaps on Epure

If Issues shows minified frames, the release string and the upload step are out of sync. Fix release + @sentry/cli before debugging Epure itself.

What works

• Browser and Node/Next JS/TS sourcemaps when release matches the uploaded artifacts.
• Demangled frames in the issue stack view after a successful upload.

Out of scope: iOS/Android symbolication, non-JS languages. Docs spine: Source maps.

Release + @sentry/cli upload

• Set the same release string in Sentry.init and in your upload step.
• Build production assets.
• Upload maps with @sentry/cli or your CI recipe pointed at the Epure host (auth token / org / project per docs).
• Deploy the build that matches that release.

Prefer concrete commands from docs/guides/source-maps for the current CLI flags on your SDK major. Do not invent flags here. Next.js: Next.js integration. Browser SPA: Browser.

Verify frames

• Trigger a known exception from minified production code.
• Open Issues, then the event stack.
• Confirm file/function names demangle. If not, check release mismatch and upload logs.

Also run the basic ingest check: Verify.

Common failures

• Release string mismatch between init and upload.
• Maps uploaded to the wrong project.
• Auth token missing upload scope.
• Deploying a different build than the one you uploaded.