fix(deps): update grafana faro to v2.5.0 #2890
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.4.0→2.5.02.4.0→2.5.0Release Notes
grafana/faro-web-sdk (@grafana/faro-web-sdk)
v2.5.0Compare Source
Fix (
@grafana/faro-web-sdk): Use monotonic clock instead of wall clock for durationmeasurements (#2016).
Fix (
@grafana/faro-core):faro.apiis now a no-op beforeinitializeFaro()runs,preventing
TypeError: faro.api is undefinedwhen accessed pre-initialization or withduplicate singleton copies (#1889).
Feature (
@grafana/faro-core): Extend TS types for new Faro spec fields —MetaOS,MetaDevice,meta.os,meta.device,meta.app.installationId, andfatalonExceptionEventDefault.meta.deviceandmeta.app.installationIdare not populatedby the Web SDK.
fatalcan be set viapushError(err, { fatal: true })and participatesin dedupe (#1997).
Feature (
@grafana/faro-web-sdk): New defaultosMetaprovider populatesmeta.os(
name,version) from the user agent. Registered automatically and re-exported forcustom meta setups (#1997).
Fix (
@grafana/faro-core): Exception dedupe now considers the stacktrace. The dedupekey previously referenced a non-existent
stackTracefield (camelCase typo), so errorswith the same message/type but different stacks were deduped. Consumers relying on
config.dedupemay see an increase in reported exceptions (#1997).Chore (
@grafana/faro-*): Pinnedprotobufjsto^8.0.1to remediate CVE-2026-41242,and updated multiple other dependencies (#2008, #2010, #2011, #2012, #2017, #2019).
Configuration
📅 Schedule: (UTC)
🚦 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 Mend Renovate.
e78edce745to64f05b795c