You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sentry's most up to date solution for sourcemaps involved adding unique IDs to your source files, which you then upload to sentry. Those IDs will be present in your stack traces as well. Greatly simplifying the ability to connect stack traces to source files, and enabling sentry to link directly to your human readable source code.
the GitHub Actions Release for Sentry use the sentry-cli, where the debugIds injections has been added, but the release action does not support it yet.
Possible need a new release of the GHA to support the latest version of the sentry-cli and expose the ability to inject debugIds. This ideally will support all platforms which support debugIds, javascript and react-native.
@smeubank Great timing! I am looking to move away from custom GHAs that run sentry-cli for the release process, and this is the only remaining gap for me.
It would be a real win to be able to support all my GitHub workflow needs from a single officially supported action.
Background:
Sentry's most up to date solution for sourcemaps involved adding unique IDs to your source files, which you then upload to sentry. Those IDs will be present in your stack traces as well. Greatly simplifying the ability to connect stack traces to source files, and enabling sentry to link directly to your human readable source code.
SDK Docs: What are Artifact Bundles
Develop Docs: Debug IDs
Task
the GitHub Actions Release for Sentry use the sentry-cli, where the debugIds injections has been added, but the release action does not support it yet.
Possible need a new release of the GHA to support the latest version of the sentry-cli and expose the ability to inject debugIds. This ideally will support all platforms which support debugIds, javascript and react-native.
Solves:
#165
#164
#159
Simplifies:
#192
The text was updated successfully, but these errors were encountered: