Bump @sentry/browser from 4.6.5 to 6.3.4

[dependabot-preview]

⚠️ Dependabot Preview has been deactivated ⚠️

This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to dependabot commands nor will it be automatically closed if a new version is found.

If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.

---

Bumps @sentry/browser from 4.6.5 to 6.3.4.

Release notes

Sourced from @​sentry/browser's releases.

6.3.4

• [nextjs] fix: API routes logging (#3479)

6.3.3

• [nextjs] fix: User server types (#3471)

6.3.2

• [nextjs] ref: Remove next.js plugin (#3462)
• [core] fix: Prevent InboundFilters mergeOptions method from breaking users code (#3458)

6.3.1

• [angular] fix: Make SentryErrorHandler extensible and export it publicly (#3438)
• [browser] feat: Capture information about the LCP element culprit (#3427)
• [core] fix: Correctly attach installed integrations to sdkinfo (#3447)
• [ember] fix: Add guards to ensure marks exist (#3436)
• [nextjs] fix: Fix incomplete merging of user config with Sentry config (#3434)
• [nextjs] ref: Use resolved paths for require calls in config code (#3426)
• [node] fix: Fix for manual tests in node (#3428)
• [transports] feat: Honor no_proxy env variable (#3412)

6.3.0

• [browser] feat: Parse safari-extension and safari-web-extension errors (#3374)
• [browser] fix: Provide better descriptions for the performance navigation timing spans (#3245)
• [browser] test: Replace Authorization with Accept header (#3400)
• [ci] ci: Add CodeQL scanning
• [core] Drop session if release is not a string or is missing and log (#3396)
• [docs] Document how to publish a new release (#3361)
• [gatsby] fix: Specify gatsby peer dep (#3385)
• [gatsby] chore(docs): Update @​sentry/gatsby README (#3384)
• [integrations] feat(integrations): add prefix support for RewriteFrames (#3416)
• [integrations] ref: Use esm imports with localforage and add esModuleInterop (#3403)
• [nextjs] feat: Next.js SDK + Plugin (#3301)
• [node] fix: Generate a Sentry Release string from env if its not provided (#3393)
• [tracing] fix: Replace performance.timeOrigin in favour of browserPerformanceTimeOrigin (#3397)
• [tracing] fix: Mark span as failed when fetch API call fails (#3351)
• [utils] fix: Use the more reliable timeOrigin (#3398)
• [utils] fix: Wrap oldOnPopState.apply call in try/catch to prevent Firefox from crashing (#3377)

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)

... (truncated)

Changelog

Sourced from @​sentry/browser's changelog.

6.3.4

• [nextjs] fix: API routes logging (#3479)

6.3.3

• [nextjs] fix: User server types (#3471)

6.3.2

• [nextjs] ref: Remove next.js plugin (#3462)
• [core] fix: Prevent InboundFilters mergeOptions method from breaking users code (#3458)

6.3.1

• [angular] fix: Make SentryErrorHandler extensible and export it publicly (#3438)
• [browser] feat: Capture information about the LCP element culprit (#3427)
• [core] fix: Correctly attach installed integrations to sdkinfo (#3447)
• [ember] fix: Add guards to ensure marks exist (#3436)
• [nextjs] fix: Fix incomplete merging of user config with Sentry config (#3434)
• [nextjs] ref: Use resolved paths for require calls in config code (#3426)
• [node] fix: Fix for manual tests in node (#3428)
• [transports] feat: Honor no_proxy env variable (#3412)

6.3.0

• [browser] feat: Parse safari-extension and safari-web-extension errors (#3374)
• [browser] fix: Provide better descriptions for the performance navigation timing spans (#3245)
• [browser] test: Replace Authorization with Accept header (#3400)
• [ci] ci: Add CodeQL scanning
• [core] Drop session if release is not a string or is missing and log (#3396)
• [docs] Document how to publish a new release (#3361)
• [gatsby] fix: Specify gatsby peer dep (#3385)
• [gatsby] chore(docs): Update @​sentry/gatsby README (#3384)
• [integrations] feat(integrations): add prefix support for RewriteFrames (#3416)
• [integrations] ref: Use esm imports with localforage and add esModuleInterop (#3403)
• [nextjs] feat: Next.js SDK + Plugin (#3301)
• [node] fix: Generate a Sentry Release string from env if its not provided (#3393)
• [tracing] fix: Replace performance.timeOrigin in favour of browserPerformanceTimeOrigin (#3397)
• [tracing] fix: Mark span as failed when fetch API call fails (#3351)
• [utils] fix: Use the more reliable timeOrigin (#3398)
• [utils] fix: Wrap oldOnPopState.apply call in try/catch to prevent Firefox from crashing (#3377)

6.2.5

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

6.2.4

• [browser] fix: Add SentryRequestType to RateLimitingCategory mapping (#3328)

... (truncated)

Commits

• 726b4aa release: 6.3.4
• db50399 fix: Set handled:false for next.js serverless
• 3fbe529 fix: next.js few fixes (#3479)
• 3ab107b fix(nextjs): Add missing changes from #3462 (#3476)
• b7382a2 misc: Change size-limit to 100kb for tracking purposes only (#3474)
• de87032 Merge release/6.3.3 into master
• ee17023 release: 6.3.3
• 3caa893 fix(nextjs): User server types (#3471)
• 472480a Merge release/6.3.2 into master
• 4aab1aa release: 6.3.2
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by sentry-bot, a new releaser for @​sentry/browser since your current version.

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 will not automatically merge this PR because it includes a major update to a production dependency.

---

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:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)