chore: upgrade Sentry

[Nodonisko]

Description

Related Issue

Resolve

Screenshots:

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 26
• More info

Learn more about 𝝠 Expo Github Action

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Network access	npm/@sentry-internal/browser-utils@9.1.0	Module: globalThis["fetch"] Location: Package overview	packages/suite-desktop-core/package.json	🚫
Network access	npm/@sentry-internal/browser-utils@8.54.0	Module: globalThis["fetch"] Location: Package overview	suite-native/app/package.json	🚫
Network access	npm/@sentry/browser@9.1.0	Module: globalThis["fetch"] Location: Package overview	packages/suite-desktop-core/package.json	🚫
Network access	npm/@sentry/browser@8.54.0	Module: globalThis["fetch"] Location: Package overview	suite-native/app/package.json	🚫

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@sentry-internal/browser-utils@9.1.0
• @SocketSecurity ignore npm/@sentry-internal/browser-utils@8.54.0
• @SocketSecurity ignore npm/@sentry/browser@9.1.0
• @SocketSecurity ignore npm/@sentry/browser@8.54.0

[matejkriz]

To preserve the original behavior with session tracking disabled, you need to remove the default integration browserSessionIntegration, in my opinion. https://docs.sentry.io/platforms/javascript/guides/react/configuration/integrations/#removing-a-default-integration

https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/#removed-apis

[Nodonisko]

Good point I was thinking it disabled by default.

[Nodonisko]

I am not happy about casting to any but I was not able to find any other way how to it.

[Nodonisko]

We need to wait until version 7 comes out because v6 is not compatible with v9 core.