Luca Forstner

I think this was already resolved. If not, feel free to clarify this issue a bit and we'll address it! Thanks!

Thoughts: - Don't capture the stack trace. It might contain PII via paths. - Don't capture error messages. They might contain PII. Use manual very bare errors instead. - We...

@adinauer Sorry, I think what I meant was you can use the CLI's `--header` option to pass along a `sentry-trace` and `baggage` header to the Sentry backend. I don't think...

Reopening this because we have to revert https://github.com/getsentry/sentry-javascript/pull/6404 because it introduced a bug (https://github.com/getsentry/sentry-javascript/issues/6504).

Ok it seems like auto release injection is a bit inconsistent on Vercel. I will get in touch with them and ask if we can bust the cache somehow. At...

@Geczy Okay, looking at your repo I see the issue that you're not setting the `release` option in the webpack plugin options with `withSentryConfig`. Can you try doing that?

@alvarlagerlof We won't be putting Vercel specific instructions into the snippet because not everybody is deploying to vercel. Can you elaborate what exactly is broken in the Next.js guide you...

@alvarlagerlof I think it's just broken for Vercel. It's related to build caches. I have a PR open to fix this.

I believe this should be fixed in recent versions. Feel free to ping me if this is not the case.

@KrisBraun Gonna happen soon™ 👀