Update dependency @sentry/browser to v8.38.0

This MR contains the following updates:

Package	Type	Update	Change
@sentry/browser (source)	dependencies	minor	8.37.1 -> 8.38.0

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

---

Release Notes

getsentry/sentry-javascript (@​sentry/browser)

v8.38.0

Compare Source

• docs: Improve docstrings for node otel integrations (#​14217)
• feat(browser): Add moduleMetadataIntegration lazy loading support (#​13817)
• feat(core): Add trpc path to context in trpcMiddleware (#​14218)
• feat(deps): Bump @​opentelemetry/instrumentation-amqplib from 0.42.0 to 0.43.0 (#​14230)
• feat(deps): Bump @​sentry/cli from 2.37.0 to 2.38.2 (#​14232)
• feat(node): Add knex integration (#​13526)
• feat(node): Add tedious integration (#​13486)
• feat(utils): Single implementation to fetch debug ids (#​14199)
• fix(browser): Avoid recording long animation frame spans starting before their parent span (#​14186)
• fix(node): Include debug_meta with ANR events (#​14203)
• fix(nuxt): Fix dynamic import rollup plugin to work with latest nitro (#​14243)
• fix(react): Support wildcard routes on React Router 6 (#​14205)
• fix(spotlight): Export spotlightBrowserIntegration from the main browser package (#​14208)
• ref(browser): Ensure start time of interaction root and child span is aligned (#​14188)
• ref(nextjs): Make build-time value injection turbopack compatible (#​14081)

Work in this release was contributed by @​grahamhency, @​Zen-cronic, @​gilisho and @​phuctm97. Thank you for your contributions!

---

Configuration

Schedule: Branch creation - "before 05:00 on Monday" (UTC), Automerge - At any time (no schedule defined).

Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.

Renovate Comment

What are the next steps?

If you have been assigned as a reviewer to this Merge Request, please review this Merge Request with the same scrutiny as any community contribution:

1. Ensure that the dependencies updated meet our standards:

   • Security: Dependencies do not contain malicious code
   • Performance: Dependencies do not bloat the application code or prolong CI times unnecessarily
   • Stability: Pipelines are passing

2. Review the changes introduced by the version upgrade. Consider using https://my.diffend.io to compare the two versions in case the updated dependency is either a Ruby Gem or a Node.js package, for example to compare pg_query 2.1.0 and 2.1.4.

3. Check if bundle install works locally, in the context of GDK.

4. If tests are passing and you've reviewed the updated dependencies, execute pipelines in the context of the main project

   This MR is created from a fork, therefore not all jobs (e.g. Danger) might have been executed. Instead of hitting MWPS right away, you might want to wait until the pipeline you've just triggered finished.

   Note: This might not be available in projects, in that case merging right away is an option

5. Assign the current milestone to the MR

6. Merge away!

Troubleshooting

We have assembled some FAQs to help reviewers of these kind of merge requests.

Improve this message – The JSON comment below is for automation purposes.

{"labels":["maintenance::dependency","type::maintenance","automation:bot-authored","frontend"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["mrincon","sheldonled"]}

mentioned in issue #365044

added automation:bot-authored frontend maintenancedependency typemaintenance labels

requested review from @mrincon and @sheldonled

assigned to @gitlab-dependency-update-bot

added 1 commit

• 2c1cf795 - Update dependency @sentry/browser to v8.38.0

Compare with previous version

LGTM

removed review request for @mrincon

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels

enabled automatic add to merge train when checks pass

resolved all threads

	1 Warning
	This merge request does not refer to an existing milestone.

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
frontend	@jmontal (UTC-7)	@sheldonled (UTC+0)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

changed milestone to %17.7

Bundle size analysis [beta]

This compares changes in bundle size for entry points between the commits 1ecc86f9 and 2c1cf795

Special assets

Entrypoint / Name	Size before	Size after	Diff	Diff in percent
average	4.41 MB	4.41 MB	-	0.0 %
mainChunk	3.32 MB	3.32 MB	-	0.0 %

---

Note: We do not have exact data for 1ecc86f9. So we have used data from: 86acefc7.
The target commit was too new, so we used the latest commit from master we have info on.
It might help to rerun the bundle-size-review job
This might mean that you have a few false positives in this report. If something unrelated to your code changes is reported, you can check this comparison in order to see if they caused this change.

Please look at the full report for more details

---

Read more about how this report works.

Generated by Danger

started a merge train

merged

mentioned in commit f051afac