Bump Sentry from 2.1.1 to 3.0.1 in /api

[dependabot-preview]

Bumps Sentry from 2.1.1 to 3.0.1.

Release notes

Sourced from Sentry's releases.

3.0.1

• bump log4net 2.0.12 (#781) @bruno-garcia
• Fix Serilog version (#780) @bruno-garcia
• Move main Protocol types to Sentry namespace (#779) @bruno-garcia

3.0.0

Breaking changes

Please read through all breaking changes relevant to you before upgrading.

!Important: Grouping Changes

The format of the stack traces were greatly improved with the help of Ben Adam's iconic library Ben.Demystifier. Frames now include details such as async, static, the actual return type, method parameters, tuples and their names, and more.

One big caveat is that this will affect grouping!. If you prefer to stay with the original stack trace format, you can opt-out of this feature with:

options.StackTraceMode = StackTraceMode.Original;

ASP.NET

ASP.NET (not Core) users need to install an additional package:

Sentry.AspNet.

Without this, HTTP related information will not be added to events.

You can plug it in to the Init as follows:

SentrySdk.Init(o =>
{
    o.AddAspNet();
});

The motivation was to remove the reference to System.Web to decouple the core of the package with any specific namespaces of the .NET Framework, which improves the experience from other environments such as game engines like Unity and Godot.

ASP.NET Core Environment Casing

To match Sentry's default environment naming convention, unless explicitly set otherwise, the Sentry environment will be reported lowercase. That means if ASPNET_ENVIRONMENT is equal to Production, the Sentry SDK will report it as production #551

IHub received two new methods

Sentry's Performance product requires additive API changes to interfaces such as IHub. If you implement your own IHub, you'll need to implement two new methods:

StartTransaction and GetTraceHeader.

DiagnosticsLogger renamed to DiagnosticLogger

... (truncated)

Changelog

Sourced from Sentry's changelog.

3.0.1

• bump log4net 2.0.12 (#781) @bruno-garcia
• Fix Serilog version (#780) @bruno-garcia
• Move main Protocol types to Sentry namespace (#779) @bruno-garcia

3.0.0

• Add support for dynamic transaction sampling. (#753) @Tyrrrz
• Integrate trace headers. (#758) @Tyrrrz
• Renamed Option DiagnosticsLevel to DiagnosticLevel (#759) @bruno-garcia
• Add additional data to transactions (#763) @Tyrrrz
• Improve transaction instrumentation on ASP.NET Core (#766) @Tyrrrz
• Add Release to Scope (#765) @Tyrrrz
• Don't fallback to HttpContext.RequestPath if a route is unknown (#767 #769) @kanadaj @Tyrrrz

3.0.0-beta.0

• Add instruction_addr to SentryStackFrame. (#744) @lucas-zimerman
• Default stack trace format: Ben.Demystifier (#732) @bruno-garcia

3.0.0-alpha.11

Changed

• Limit attachment size (#705)
• Separate tracing middleware (#737)
• Bring Transaction a bit more inline with Java SDK (#741)
• Sync transaction and transaction name on scope (#740)

3.0.0-alpha.10

• Disabled Mono StackTrace Factory. (#709) @lucas-zimerman
• Adds to the existing User Other dict rather than replacing (#729) @brettjenkins

3.0.0-alpha.9

• Handle non-json error response messages on HttpTransport. (#690) @lucas-zimerman
• Fix deadlock on missing ConfigureAwait into foreach loops. (#694) @lucas-zimerman
• Report gRPC sdk name (#700) @bruno-garcia

3.0.0-alpha.8

• Include parameters in stack frames. (#662) @Tyrrrz
• Remove CultureUIInfo if value is even with CultureInfo. (#671) @lucas-zimerman
• Make all fields on UserFeedback optional. (#660) @Tyrrrz
• Align transaction names with Java. (#659) @Tyrrrz
• Include assembly name in default release. (#682) @Tyrrrz
• Add support for attachments. (#670) @Tyrrrz
• Improve logging for relay errors. (#683) @Tyrrrz

... (truncated)

Commits

• 46c440e release: 3.0.1
• 4e41189 bump log4net 2.0.10 (#781)
• e2e1947 Fix Serilog version (#780)
• 3968035 Move types to Sentry namespace (#779)
• 6d9c229 remove unused proj (#777)
• bcc12cb 3.0.0
• 3248ce4 Refactor last PR (#769)
• 311c7e0 Group unknown routes (#767)
• 248e7b8 add tyrrrz codeowners (#768)
• aed8894 Improve transaction instrumentation on ASP.NET Core (#766)
• 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:

• 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)

[dependabot-preview]

Superseded by #148.