Sentry Changelog

Code mappings connect your stack traces to source code, enabling features like source context, suspect commits, and stack trace linking. Previously, you had to configure them one-by-one through the Sentry UI — tedious for monorepos with dozens of modules.

You can now upload code mappings in bulk using sentry-cli:

sentry-cli code-mappings upload ./mappings.json

The JSON file pairs stack trace roots with their source paths in your repository:

[
  {"stackRoot": "io/sentry/android/core", "sourceRoot": "sentry-android-core/src/main/java/io/sentry/android/core"},
  {"stackRoot": "io/sentry/opentelemetry", "sourceRoot": "sentry-opentelemetry/sentry-opentelemetry-core/src/main/java/io/sentry/opentelemetry"},
  {"stackRoot": "io/sentry/opentelemetry", "sourceRoot": "sentry-opentelemetry/sentry-opentelemetry-bootstrap/src/main/java/io/sentry/opentelemetry"}
]

Multiple mappings can share the same stack root — useful when the same package prefix exists across multiple modules (like io/sentry/opentelemetry above).

Generating Mappings for Gradle Projects

For Android/JVM projects, you can generate the mappings JSON from your Gradle build. Add this task to your root build.gradle.kts:

abstract  GenerateSentryMappingsTask   

Then run:

./gradlew generateSentryMappings

sentry-cli code-mappings upload ./sentry-mappings.json

What You Get

• Source context and stack trace linking for all modules without manual setup
• Suspect commits and code owners working across your entire monorepo
• CI/CD friendly — keep mappings in sync as your project structure evolves

Check our docs for more details.