search

DirtyRacer1337 / Jellyfin.Plugin.PhoenixAdult

Jellyfin/Emby Metadata Provider for videos from multiple adult sites
GNU General Public License v2.0
348 stars 46 forks source link

Bump Sentry.AspNetCore from 3.39.1 to 3.40.0 #240

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps Sentry.AspNetCore from 3.39.1 to 3.40.0.

Release notes

Sourced from Sentry.AspNetCore's releases.

3.40.0

Obsoletion

  • WithScope and WithScopeAsync have been proven to not work correctly in desktop contexts when using a global scope. They are now deprecated in favor of the overloads of CaptureEvent, CaptureMessage, and CaptureException. Those methods provide a callback to a configurable scope. (#2677)
  • StackFrame.InstructionOffset has not been used in the SDK and has been ignored on the server for years. (#2689)

Features

  • Release of Azure Functions (Isolated Worker/Out-of-Process) support (#2686)

Fixes

  • Scope is now correctly applied to Transactions when using OpenTelemetry on ASP.NET Core (#2690)

Dependencies

3.40.0-beta.0

Features

  • Reduced the memory footprint of SpanId by refactoring the ID generation (2619)
  • Reduced the memory footprint of SpanTracer by initializing the tags lazily (2636)
  • Added distributed tracing without performance for Azure Function Workers (#2630)
  • The SDK now provides and overload of ContinueTrace that accepts headers as string (#2601)
  • Sentry tracing middleware now gets configured automatically (#2602)

Fixes

  • Resolved issue identifying users with OpenTelemetry (#2618)

Azure Functions Beta

  • Package name changed from Sentry.AzureFunctions.Worker to Sentry.Azure.Functions.Worker. Note AzureFunctions now is split by a .. (#2637)

Dependencies

Changelog

Sourced from Sentry.AspNetCore's changelog.

3.40.0

Obsoletion

  • WithScope and WithScopeAsync have been proven to not work correctly in desktop contexts when using a global scope. They are now deprecated in favor of the overloads of CaptureEvent, CaptureMessage, and CaptureException. Those methods provide a callback to a configurable scope. (#2677)
  • StackFrame.InstructionOffset has not been used in the SDK and has been ignored on the server for years. (#2689)

Features

  • Release of Azure Functions (Isolated Worker/Out-of-Process) support (#2686)

Fixes

  • Scope is now correctly applied to Transactions when using OpenTelemetry on ASP.NET Core (#2690)

Dependencies

3.40.0-beta.0

Features

  • Reduced the memory footprint of SpanId by refactoring the ID generation (2619)
  • Reduced the memory footprint of SpanTracer by initializing the tags lazily (2636)
  • Added distributed tracing without performance for Azure Function Workers (#2630)
  • The SDK now provides and overload of ContinueTrace that accepts headers as string (#2601)
  • Sentry tracing middleware now gets configured automatically (#2602)
  • Added memory optimisations for GetLastActiveSpan (#2642)

Fixes

  • Resolved issue identifying users with OpenTelemetry (#2618)

Azure Functions Beta

  • Package name changed from Sentry.AzureFunctions.Worker to Sentry.Azure.Functions.Worker. Note AzureFunctions now is split by a .. (#2637)

Dependencies

... (truncated)

Commits
  • 5687e70 release: 3.40.0
  • 41714ae Apply Scope to exceptions captured via Activity.RecordException (#2712)
  • 46f6d25 Delete SentryAzureFunctions.slnf (#2708)
  • 89a50ab Fix: Scope not being applied to OpenTelemetry spans in ASP.NET Core (#2690)
  • ed6d161 build(deps): bump styfle/cancel-workflow-action from 0.11.0 to 0.12.0 (#2707)
  • 407dc28 chore: update scripts/update-cli.ps1 to 2.21.2 (#2698)
  • 8cd3194 chore: obsolete StackFrame.InstructionOffset (#2689)
  • bf4e0b3 Added http.request.method and http.response.status_code to span data/extras (...
  • 11f43e9 Made SpanTracer.InternalTags an autoproperty (#2682)
  • 8ad54c7 build(deps): bump gradle/gradle-build-action from 2.8.0 to 2.9.0 (#2687)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)