Luca Forstner

@alipek Can you also verify that this is due to some special characters in the release name?

@szokeasaurusrex maybe we can improve the error message in Sentry CLI? Suggestion: > error: Release not found. Verify that you have configured the right organization and project for this operation.

Unfortunately, due to limitations of the esbuilds plugin system we currently cannot make it deterministic - unless we modify files after the fact. This is possible but a major PITA...

As a workaround you can also use the legacy process (which doesn't inject anything) or Sentry CLI, which should be deterministic when injecting.

> The workaround I've implemented right now is pulling the sentry debug IDs out of the build artifacts from our CI system and writing them to a file That's pretty...

Hi, thanks for writing in. We will most likely not dedicate much time to this in the short to medium-term future. For posterity, I used the banner plugin because it...

I am contemplating whether we should just remove unplugin entirely. In the beginning, I thought it was a good idea to abstract away all the bundler intricacies but by now...

No updates. I think we are soft-blocked by https://github.com/unjs/unplugin/issues/323. We could remove the `unplugin` dependency but it would result in quite a bit of work which we don't have the...

@krema Not yet. You can use Sentry CLI to upload source maps for now. There also seems to be an issue with angular and esbuild in general. https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/351

@rgant Using `"@sentry/webpack-plugin": "^1.21.0"` is perfectly fine!