fix(deps): update grafana faro to v2 (major) #2697

2025-12-02T20:04:58Z

group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented

2025-12-02 20:04:58 +00:00

(Migrated from gitlab.com)

This MR contains the following updates:

Package	Change	Age	Confidence
@grafana/faro-web-sdk (source)	`1.19.0` -> `2.0.2`
@grafana/faro-web-tracing (source)	`1.19.0` -> `2.0.2`

Release Notes

grafana/faro-web-sdk (@grafana/faro-web-sdk)

`v2.0.2`

Compare Source

Breaking (@grafana/faro-web-sdk): User action events now have a standardized event name
(faro.user.action), with the specific user action name moved to a parameter for improved
consistency and filtering capabilities.
Migration note: If you previously filtered user action events by event name, update your
queries to use the new event name (faro.user.action) and filter by the userActionName
attribute for the specific action.
Breaking (@grafana/faro-web-sdk): Web vitals now always tracks attribution data. The
trackWebVitalsAttribution and webVitalsInstrumentation.trackAttribution configuration flags have
been removed. Attribution data is now collected by default and cannot be disabled.
Migration note: If you were using trackWebVitalsAttribution: false or
webVitalsInstrumentation: { trackAttribution: false } to disable attribution, remove these options
from your configuration. Attribution data will now always be included in web vitals measurements.
Breaking (@grafana/faro-web-sdk): Removed the trackUserActionsPreview option from Faro
configuration. User actions instrumentation is now always enabled by default (#1772).
Migration note: If you previously used trackUserActionsPreview: true or left it unset,
simply remove this option - no further action is required. If you had set
trackUserActionsPreview: false to disable user actions tracking, you now need to exclude the
UserActionInstrumentation from your instrumentations array manually.
Feature (@grafana/faro-web-sdk) [experimental]: Added navigation instrumentation to track soft
navigations (same-document navigations). The instrumentation monitors URL changes, DOM mutations,
HTTP requests, and user interactions to automatically detect and report navigation events with
details including fromUrl, toUrl, and duration. Enable by setting experimental.trackNavigation: true
in the configuration.
Fix (@grafana/faro-web-sdk): Fixed an issue where custom severity and custom trigger properties
were not being included in user action attributes (#1551)
Fix (@grafana/faro-web-sdk): Fixed an error when initializeFaro is called without any window
object present (#1643)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.

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

This MR has been generated by Renovate Bot.

This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@grafana/faro-web-sdk](https://github.com/grafana/faro-web-sdk) ([source](https://github.com/grafana/faro-web-sdk/tree/HEAD/packages/web-sdk)) | [`1.19.0` -> `2.0.2`](https://renovatebot.com/diffs/npm/@grafana%2ffaro-web-sdk/1.19.0/2.0.2) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@grafana%2ffaro-web-sdk/2.0.2?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@grafana%2ffaro-web-sdk/1.19.0/2.0.2?slim=true) | | [@grafana/faro-web-tracing](https://github.com/grafana/faro-web-sdk) ([source](https://github.com/grafana/faro-web-sdk/tree/HEAD/packages/web-tracing)) | [`1.19.0` -> `2.0.2`](https://renovatebot.com/diffs/npm/@grafana%2ffaro-web-tracing/1.19.0/2.0.2) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@grafana%2ffaro-web-tracing/2.0.2?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@grafana%2ffaro-web-tracing/1.19.0/2.0.2?slim=true) | --- ### Release Notes <details> <summary>grafana/faro-web-sdk (@grafana/faro-web-sdk)</summary> ### [`v2.0.2`](https://github.com/grafana/faro-web-sdk/blob/HEAD/CHANGELOG.md#202) [Compare Source](https://github.com/grafana/faro-web-sdk/compare/v1.19.0...v2.0.2) - Breaking (`@grafana/faro-web-sdk`): User action events now have a standardized event name (`faro.user.action`), with the specific user action name moved to a parameter for improved consistency and filtering capabilities. **Migration note:** If you previously filtered user action events by event name, update your queries to use the new event name (`faro.user.action`) and filter by the `userActionName` attribute for the specific action. - Breaking (`@grafana/faro-web-sdk`): Web vitals now always tracks attribution data. The `trackWebVitalsAttribution` and `webVitalsInstrumentation.trackAttribution` configuration flags have been removed. Attribution data is now collected by default and cannot be disabled. **Migration note:** If you were using `trackWebVitalsAttribution: false` or `webVitalsInstrumentation: { trackAttribution: false }` to disable attribution, remove these options from your configuration. Attribution data will now always be included in web vitals measurements. - Breaking (`@grafana/faro-web-sdk`): Removed the `trackUserActionsPreview` option from Faro configuration. User actions instrumentation is now always enabled by default ([#1772](https://github.com/grafana/faro-web-sdk/issues/1772)). **Migration note:** If you previously used `trackUserActionsPreview: true` or left it unset, simply remove this option - no further action is required. If you had set `trackUserActionsPreview: false` to disable user actions tracking, you now need to exclude the `UserActionInstrumentation` from your instrumentations array manually. - Feature (`@grafana/faro-web-sdk`) \[experimental]: Added navigation instrumentation to track soft navigations (same-document navigations). The instrumentation monitors URL changes, DOM mutations, HTTP requests, and user interactions to automatically detect and report navigation events with details including fromUrl, toUrl, and duration. Enable by setting `experimental.trackNavigation: true` in the configuration. - Fix (`@grafana/faro-web-sdk`): Fixed an issue where custom severity and custom trigger properties were not being included in user action attributes ([#1551](https://github.com/grafana/faro-web-sdk/issues/1551)) - Fix (`@grafana/faro-web-sdk`): Fixed an error when `initializeFaro` is called without any window object present ([#1643](https://github.com/grafana/faro-web-sdk/issues/1643)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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 these updates again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented

2025-12-02 20:05:01 +00:00

(Migrated from gitlab.com)

mentioned in issue #49

argoyle (Migrated from gitlab.com) merged commit b1971d1be2 into main

2025-12-03 05:08:00 +00:00

argoyle commented

2025-12-03 05:08:01 +00:00

(Migrated from gitlab.com)

mentioned in commit b1971d1be2

mentioned in commit b1971d1be2dace6a78a2138d905d6f19f1bc8f25

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dancefinder/dancefinder-app#2697