deps: Bump Sentry bundler plugins

[lforst]

Includes a few fixes and stuff.

Fixes #13504

[github-actions]

size-limit report 📦

Path	Size	% Change	Change
@sentry/browser	22.52 KB	-	-
@sentry/browser (incl. Tracing)	34.85 KB	-	-
@sentry/browser (incl. Tracing, Replay)	71.27 KB	-	-
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	64.54 KB	-	-
@sentry/browser (incl. Tracing, Replay with Canvas)	75.62 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback)	88.35 KB	-	-
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	90.18 KB	-	-
@sentry/browser (incl. metrics)	26.83 KB	-	-
@sentry/browser (incl. Feedback)	39.59 KB	-	-
@sentry/browser (incl. sendFeedback)	27.18 KB	-	-
@sentry/browser (incl. FeedbackAsync)	31.9 KB	-	-
@sentry/react	25.28 KB	-	-
@sentry/react (incl. Tracing)	37.83 KB	-	-
@sentry/vue	26.66 KB	-	-
@sentry/vue (incl. Tracing)	36.68 KB	-	-
@sentry/svelte	22.65 KB	-	-
CDN Bundle	23.77 KB	-	-
CDN Bundle (incl. Tracing)	36.53 KB	-	-
CDN Bundle (incl. Tracing, Replay)	70.91 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback)	76.22 KB	-	-
CDN Bundle - uncompressed	69.61 KB	-	-
CDN Bundle (incl. Tracing) - uncompressed	108.28 KB	-	-
CDN Bundle (incl. Tracing, Replay) - uncompressed	219.8 KB	-	-
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	232.99 KB	-	-
@sentry/nextjs (client)	37.6 KB	-	-
@sentry/sveltekit (client)	35.45 KB	+0.02%	+5 B 🔺
@sentry/node	115.75 KB	-0.14%	-157 B 🔽
@sentry/node - without tracing	89.88 KB	-0.16%	-141 B 🔽
@sentry/aws-serverless	99.29 KB	-0.16%	-159 B 🔽

View base workflow run

[mydea]

Question: Is there a reason to not use ^ version ranges for the bundler plugins? I feel like it has always to be safe to use a newer minor/patch version of the plugins, as we cannot have breaking changes there anyhow...?

ref #13504

[lforst]

Question: Is there a reason to not use ^ version ranges for the bundler plugins? I feel like it has always to be safe to use a newer minor/patch version of the plugins, as we cannot have breaking changes there anyhow...?

ref #13504

Anecdoally, I have found it better to have exact control over what versions are used.

[mydea]

Question: Is there a reason to not use ^ version ranges for the bundler plugins? I feel like it has always to be safe to use a newer minor/patch version of the plugins, as we cannot have breaking changes there anyhow...?
ref #13504

Anecdoally, I have found it better to have exact control over what versions are used.

We can think about revisiting this in the future - maybe it will safe us some time (no need to bump this all the time for fixes etc.). But it's totally fine right now, let's get this merged :D

[lforst]

let's get this merged :D

I would love to but this gives me the most cryptic CI errors that I have ever seen lolsob

[lforst]

This PR is cursed. Burn in hell.