What is the difference between SENTRY_RELEASE and __SENTRY__.hub._stack[0].client._options.release?

[Sc4ramouche]

Hi all! I have a question regarding how Sentry identifies the release data. I stumbled upon two options:

• SENTRY_RELEASE global object.
• __SENTRY__.hub._stack[0].client._options.release Sentry client object.

I noticed that in our setup those two values can be different if I print them with the following util:

function printReleaseVersion() {
    console.log('SENTRY_RELEASE:', SENTRY_RELEASE)
    console.log('Sentry client:', __SENTRY__.hub._stack[0].client._options.release)
}

Therefore I am curious what is the difference between the two and which one does Sentry use when an error event is sent.

Additional context — currently I am trying to make source maps to work in our microfrontends setup. Every MFE is it's own repo and we set release based on the latest commit sha for every MFE. However, when navigating from one MFE to another in the browser, I noticed that release can get out of sync, i.e. SENTRY_RELEASE displaying release of the MFE that I had navigated from. I assume that incorrect release data can be a major problem for source maps to work correctly, thus wanted extend my knowledge regarding release here.

Any input is welcome, thank you!

[lforst]

• __SENTRY__.hub._stack[0].client._options.release is the release value that was passed to the client. Do under no circumstances depend on this.
• SENTRY_RELEASE is the release value injected into your bundles by one of the Sentry bundler plugins. Also do not depend on this but it is at least a little bit more safe.

You don't need a correct release value if you are using the new(ish) Debug ID process to upload sourcemaps.

[Sc4ramouche]

Thanks a lot for the answer here! We do use Debug ID, added thanks to Webpack Sentry plugin.

However source maps are associated to a release when they are uploaded, aren't they? Therefore, if my understanding is correct, the following is possible:

• Runtime issue has Debug ID attached;
• A release exist, where some source map have corresponding Debug ID;
• But if runtime issue has release value mismatched, Debug ID will never be applied to the proper bundle of source maps.

Would appreciate if you could confirm if my understanding is correct or am I missing something in this picture.

[lforst]

Debug IDs always have precedence over a release value. Even with a release mismatch, sourcemaps with matching debug IDs will be applied.