Bump @sentry/integrations from 6.2.0 to 6.2.5

[dependabot-preview[bot]]

Bumps @sentry/integrations from 6.2.0 to 6.2.5.

Release notes

Sourced from @sentry/integrations's releases.

6.2.5

• [utils] fix: Avoid performance.timeOrigin if too skewed (#3356)

6.2.4

• [browser] fix: Add SentryRequestType to RateLimitingCategory mapping (#3328)
• [browser] ref: Add fast-path to fetchImpl and cleanup redundant iframe (#3341)
• [node] fix: Fallback to empty string if req.baseUrl is empty (#3329)
• [node] ref: Remove circular dependency in @sentry/node (#3335)
• [tracing] fix: Attach mysql tracing to Connection.createQuery instead of Connection.prototype.query (#3353)
• [tracing] ref: Clarify naming in BrowserTracing integration (#3338)
• [ember] ref: Fix tests to be forward compatible with component changes (#3347)
• [ember] ref: Silence deprecation warnings in beta (#3346)

6.2.3

• [gatsby] fix: Update Vercel environment variables to match their current system variables (#3337)

6.2.2

• [hub] fix: Only create sessions if the correct methods are defined (#3281)
• [core] fix: Don't override SDK metadata (#3304)
• [browser] fix: Prevent fetch errors loops with invalid fetch implementations (#3318)
• [serverless] ref: Add compatible runtime nodejs14.x to building awslambda layer (#3303)
• [ember] fix: Keep route hook context when performance-wrapping (#3274)
• [integrations] fix: Normalized Event before caching. (#3305)

6.2.1

• [core] fix: Moves SDK metadata-setting into the NodeClient/BrowserClient to protect it from being overwritten by other classes extending BaseClient like @sentry/serverless (#3279)

Changelog

Sourced from @sentry/integrations's changelog.

6.2.5

• [utils] fix: Avoid performance.timeOrigin if too skewed (#3356)

6.2.4

• [browser] fix: Add SentryRequestType to RateLimitingCategory mapping (#3328)
• [browser] ref: Add fast-path to fetchImpl and cleanup redundant iframe (#3341)
• [node] fix: Fallback to empty string if req.baseUrl is empty (#3329)
• [node] ref: Remove circular dependency in @sentry/node (#3335)
• [tracing] fix: Attach mysql tracing to Connection.createQuery instead of Connection.prototype.query (#3353)
• [tracing] ref: Clarify naming in BrowserTracing integration (#3338)
• [ember] ref: Fix tests to be forward compatible with component changes (#3347)
• [ember] ref: Silence deprecation warnings in beta (#3346)

6.2.3

• [gatsby] fix: Update Vercel environment variables to match their current system variables (#3337)

6.2.2

• [hub] fix: Only create sessions if the correct methods are defined (#3281)
• [core] fix: Don't override SDK metadata (#3304)
• [browser] fix: Prevent fetch errors loops with invalid fetch implementations (#3318)
• [serverless] ref: Add compatible runtime nodejs14.x to building awslambda layer (#3303)
• [ember] fix: Keep route hook context when performance-wrapping (#3274)
• [integrations] fix: Normalized Event before caching. (#3305)

6.2.1

• [core] fix: Moves SDK metadata-setting into the NodeClient/BrowserClient to protect it from being overwritten by other classes extending BaseClient like @sentry/serverless (#3279)

Commits

• 1b59574 release: 6.2.5
• a4f0b45 misc: CHANGELOG for 6.2.5
• dece89a fix: Avoid performance.timeOrigin if too skewed (#3356)
• 28c540c Merge release/6.2.4 into master
• 40eab2e release: 6.2.4
• 6e6786f misc: Refresh yarn.lock to lock deps for CI
• 007e62f misc: Update @sentry/react dependencies to fix types issue vol. 2
• 3556d73 misc: Update @sentry/react dependencies to fix types issue
• 9e9f2a4 misc: 6.2.4 changelog
• a081cdf fix: Attach mysql tracing to Connection.createQuery instead of Connection.pro...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #383.