Skip to content
This repository has been archived by the owner on Jun 25, 2022. It is now read-only.

[Snyk] Upgrade @sentry/browser from 5.10.2 to 5.11.0 #15

Merged
merged 1 commit into from
Feb 7, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade @sentry/browser from 5.10.2 to 5.11.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 8 days ago, on 2020-01-08.
Release notes
Package name: @sentry/browser
  • 5.11.0 - 2020-01-08
    • [apm] fix: Always attach contexts.trace to finished transaction (#2353)
    • [integrations] fix: Make RewriteFrame integration process all exceptions (#2362)
    • [node] ref: Update agent-base to 5.0 to remove http/s patching (#2355)
    • [browser] feat: Set headers from options in XHR/fetch transport (#2363)
  • 5.10.2 - 2019-12-09
    • [browser] fix: Always trigger default browser onerror handler (#2348)
    • [browser] fix: Restore correct functionToString behavior for updated fill method (#2346)
    • [integrations] ref: Allow for backslashes in unix paths (#2319)
    • [integrations] feat: Support Windows-style path in RewriteFrame iteratee (#2319)
from @sentry/browser GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@Asthriona Asthriona merged commit 69feb9c into master Feb 7, 2020
@Asthriona Asthriona deleted the snyk-upgrade-4f023ffaf60413a79c4774dd26182106 branch February 7, 2020 09:35
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants