fix(deps): update grafana faro to v2.2.3 #2779
Reference in New Issue
Block a user
Delete Branch "renovate/grafana-faro"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.2.2→2.2.32.2.2→2.2.3Release Notes
grafana/faro-web-sdk (@grafana/faro-web-sdk)
v2.2.3Compare Source
Feature (
@grafana/faro-react): AddcreateReactRouterV7OptionsandcreateReactRouterV7DataOptionshelper functions for easier React Router v7configuration (#1879).
Fix (
@grafana/faro-react): Migrated from new JSX transform (react-jsx) to classic JSX transform(
react) to prevent bundlingreact/jsx-runtimewith the package. This fixes compatibility issueswith React 19 and older React versions where bundled JSX runtime could cause breakage. React and
react-dom are now properly treated as external peer dependencies in all bundle formats (#1878).
Fix (
@grafana/faro-web-tracing): Fixed a race condition wherefaro.tracing.*events werealways sent via the global Faro instance instead of the SDK instance associated with the
FaroTraceExporter. This caused events to be incorrectly attributed in multi-instance setups
(#1874).
Chore (
@grafana/faro-core,@grafana/faro-web-sdk): SDK name(
meta.sdk.name) is now included in payload metadata alongsideversion. The SDK name is set to
faro-webin web-sdk configuration. If web sdk meta was included manually previously,
it could potentially be breaking as instrumentation metas are removed
and sdk name changed from
@grafana/faro-coretofaro-web(#1865).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.