CLI-153 Fix sourcemap upload

[damien-urruty-sonarsource]

No description provided.

[hashicorp-vault-sonar-prod]

CLI-153

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 Dependency risks

Measures
0 Security Hotspots
80.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonar-review-alpha]

Summary

Refactors sourcemap generation and Sentry integration to work within bun's build constraints. The CLI binaries are now built without external sourcemaps (producing single-file executables), while sourcemaps are generated separately in a follow-up build step specifically for Sentry upload. This prevents the conflict between bun's --compile flag and external sourcemaps. Also disables Sentry initialization during test runs to prevent unintended telemetry.

What reviewers should know

Key architectural change: The sourcemap upload workflow is now split into two stages: (1) build and publish binaries without sourcemaps in the build job, (2) rebuild with sourcemaps and upload to Sentry in the publish-binaries job. This preserves the small, single-file executable format while still uploading debug symbols to Sentry. Test safety: The SONARQUBE_CLI_DISABLE_SENTRY environment variable gates Sentry initialization, so test runs don't send telemetry. Look at the workflow changes to understand the job orchestration, then check src/lib/sentry.ts for the guard condition, and package.json to see how tests now disable Sentry.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

Conclusion: The restructuring is well-reasoned — bun's --compile flag doesn't support external sourcemaps, so separating the sourcemap generation into a dedicated rebuild is the right approach. One bug needs fixing before merge.

🗣️ Give feedback