fix(deps): update grafana faro to v2.4.0 #2873
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.3.1→2.4.02.3.1→2.4.0Release Notes
grafana/faro-web-sdk (@grafana/faro-web-sdk)
v2.4.0Compare Source
Feature (
@grafana/faro-transport-otlp-http[experimental]): OTLP HTTP transport now supports async dynamic header values.Each header value can be a function returning
Promise<string>, resolved at request time(e.g. for token refresh). Sync dynamic headers (
() => string) continue to work (#1490).Feature (
@grafana/faro-instrumentation-replay): Emit afaro.session_recording.startedFaroevent when rrweb session recording successfully starts, so backends can identify which sessions
have an associated recording (#1925).
Fix (
@grafana/faro-web-sdk):getErrorDetailsnow preserves thetypefield forErrorsubclasses (e.g.
TypeError,RangeError,SyntaxError) when captured viaconsole.erroror the global error handler (#1971).
Chore (
@grafana/faro-*): Updated multiple dependencies to address security vulnerabilities(#1973, #1969, #1976, #1980, #1968, #1965).
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 Renovate Bot.