Chore: Bump Npgsql, RestSharp, Sentry and System.Resources.Extensions#181
Closed
dependabot[bot] wants to merge 1 commit intoeros-developfrom
Closed
Conversation
Bumps Npgsql from 9.0.3 to 10.0.1 Bumps RestSharp from 106.15.0 to 114.0.0 Bumps Sentry from 4.0.2 to 6.1.0 Bumps System.Resources.Extensions from 10.0.1 to 10.0.3 --- updated-dependencies: - dependency-name: System.Resources.Extensions dependency-version: 10.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-nuget-updates - dependency-name: Npgsql dependency-version: 10.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-nuget-updates - dependency-name: Sentry dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-nuget-updates - dependency-name: Npgsql dependency-version: 10.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-nuget-updates - dependency-name: RestSharp dependency-version: 114.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: all-nuget-updates ... Signed-off-by: dependabot[bot] <[email protected]>
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updated Npgsql from 9.0.3 to 10.0.1.
Release notes
Sourced from Npgsql's releases.
10.0.1
v9.0.4 contains several minor bug fixes.
Milestone issues
Full Changelog: npgsql/npgsql@v10.0.0...v10.0.1
10.0.0
See the release notes.
The full list of changes is available here.
What's Changed
... (truncated)
10.0.0-rc.1
9.0.4
v9.0.4 contains several minor bug fixes.
Milestone issues
Full Changelog: npgsql/npgsql@v9.0.3...v9.0.4
Commits viewable in compare view.
Updated RestSharp from 106.15.0 to 114.0.0.
Release notes
Sourced from RestSharp's releases.
114.0.0
What's Changed
Full Changelog: restsharp/RestSharp@113.1.0...114.0.0
113.0
What's Changed
404response code means succes by @jnoordsij in Remove note that404response code means succes restsharp/RestSharp#2281New Contributors
404response code means succes restsharp/RestSharp#2281Full Changelog: restsharp/RestSharp@112.1.0...113.0.0
112.1.0
\tfrom invalid header value characters as the aim was to handle CRLFFull Changelog: restsharp/RestSharp@112.0.0...112.1.0
112.0.0
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.4.1...112.0.0
111.4.1
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.4.0...111.4.1
111.4.0
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.3.0...111.4.0
111.3.0
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@111.2.0...111.3.0
111.2.0
What's Changed
Execute(request)without methodFull Changelog: restsharp/RestSharp@111.1.0...111.2.0
111.0.0
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@110.2.0...111.0.0
110.2.0
What's Changed
Full Changelog: restsharp/RestSharp@110.1.0...110.2.0
110.1.0
What's Changed
AddJsonBodyoverload to serialise top-level string by @alexeyzimarev in AddAddJsonBodyoverload to serialise top-level string restsharp/RestSharp#2043Full Changelog: restsharp/RestSharp@110.0.0...110.1.0
110.0.0
What's Changed
Breaking change
The
IRestClientinterface signature is different, so any non-standard implementations need to adopt the changes.To keep
DefaultParametersthread-safe, it got a new typeDefaultParameters, and request propertyParametershas a dedicated typeRequestParameter. Code-wise the change is non-breaking as the signatures are the same, but v110 is not binary compatible with previous versions. The difference is thatDefaultParameterscollection wraps all its mutations in a lock.Full Changelog: restsharp/RestSharp@109.0.1...110.0.0
109.0.1
What's Changed
HttpClient. by @tacosontitan in Fixed a bug causing duplicate user-agent headers when using a sharedHttpClient. restsharp/RestSharp#2008New Contributors
HttpClient. restsharp/RestSharp#2008Full Changelog: restsharp/RestSharp@109.0.0...109.0.1
109.0.0
What's Changed
JwtAuthenticatorwith token includes Bearer prefix by @nivmeshorer in Support constructing JwtAuthenticator with token includes Bearer prefix restsharp/RestSharp#1949CsvConfigurationwhen reading by @electrokit in Use supplied CsvConfiguration when reading restsharp/RestSharp#1965RequestMessageby @adegwerth in fixed access to possible null object RequestMessage restsharp/RestSharp#1989RestRequestExtension.csby @ztl8702 in cleanup: Fix parameter naming case inconsistency inRestRequestExtension.csrestsharp/RestSharp#1986IRestClientinterfaceOptionsproperty is using read-only options class, so it won't be possible to re-assign options that configure HTTP client and message handlerNew Contributors
RestRequestExtension.csrestsharp/RestSharp#1986Full Changelog: restsharp/RestSharp@108.0.3...109.0.0
108.0.3
What's Changed
AddFile(#1953)New Contributors
Full Changelog: restsharp/RestSharp@108.0.2...108.0.3
108.0.2
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@108.0.1...108.0.2
108.0.1
Full Changelog: restsharp/RestSharp@108.0.0...108.0.1
108.0.0
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@107.3.0...108.0.0
107.3.0
What's Changed
CompletedNew Contributors
Full Changelog: restsharp/RestSharp@107.2.1...107.3.0
107.2.1
AddCookiefailing with null value as cookie domain107.2.0
What's Changed
New Contributors
Full Changelog: restsharp/RestSharp@107.1.2...107.2.0
107.1.2
Acceptheader values #1707HttpClientdisposal #1711107.1.1
What's Changed
DataType.Binaryand corresponding body handlingGetJsonAsync, etc)SEARCHverb handlingFull Changelog: restsharp/RestSharp@107.0.3...107.1.1
107.0.3
EncodingfromRestClientOptions(default utf-8)ThrowOnAnyErrorbeing ignored for unsuccessful calls107.0.2
What's Changed
x-www-form-urlencodedby default unless there's a body or multipart form is set in optionsDisableCharsetto make servers that don't support charset inContent-Typehappierstructas part of #1682 fixRestResponse.ContentHeaderscollection #1684usingfor #1685Full Changelog: restsharp/RestSharp@107.0.1...107.0.2
107.0.1
What's Changed
Full Changelog: restsharp/RestSharp@107.0.0...107.0.1
107.0.0
First preview release using HttpClient.
Check the initial migration guide.
This release includes major breaking changes:
IRestClientis removed, useRestClientclass insteadIRestRequestis removed, useRestRequestclass insteadIRestResponseis removed, useRestResponseclass insteadRestClientOptionsas they can't be changed after creating theHttpMessageHandlerinstanceParameteris now an abstract record. Use specific parameter types likeQueryParameterSystem.Text.Json, SimpleJson is gone107.0.0-preview.1
First preview release using
HttpClient.This release includes major breaking changes:
IRestClientis removed, useRestClientclass insteadIRestRequestis removed, useRestRequestclass insteadIRestResponseis removed, useRestResponseclass insteadRestClientOptionsas they can't be changed after creating theHttpMessageHandlerinstanceSystem.Text.Json,SimpleJsonis goneCommits viewable in compare view.
Updated Sentry from 4.0.2 to 6.1.0.
Release notes
Sourced from Sentry's releases.
6.1.0
Features
SentryThreadbyMainto allow indication whether the thread is considered the current main thread (#4807)Fixes
EnvironmentandRelease(#4883)Dependencies
6.1.0-alpha.2
BREAKING CHANGES
AddCountertoEmitCounterRecordDistributiontoEmitDistributionRecordGaugetoEmitGaugeFeatures
Fixes
SetBeforeSendLogcallback (#4834)decimal) for Trace-connected Metrics (#4834)6.1.0-alpha.1
Features
SentryThreadbyMainto allow indication whether the thread is considered the current main thread (#4807)Dependencies
6.0.0
BREAKING CHANGES
SentryLoggingOptions.ExperimentalLogging.MinimumLogLevel. Structured Logs can now be configured via the"Sentry"logging provider (e.g. inappsettings.jsonandappsettings.{HostEnvironment}.json) (#4700)SentryLog.ParentSpanIdtoSentryLog.SpanIdreflecting the protocol change (#4778)IDisposableso that they can be used withusingstatements/declarations that will automatically finish the span with a status of OK when it passes out of scope, if it has not already been finished, to be consistent withActivityclasses when using OpenTelemetry (#4627)sealed(see also #4627)ExperimentalfromSentryOptions(#4699)SentryIdand aCaptureFeedbackResultout parameter that indicate whether feedback was captured successfully and what the reason for failure was otherwise (#4613)Sentry.Azure.Functions.Workeras very few people were using it and the functionality can easily be replaced with OpenTelemetry. We've replaced our integration with a sample showing how to do this using our OpenTelemetry package instead. (#4693)BreadcrumbLevel.Criticalhas been renamed toBreadcrumbLevel.Fatalfor consistency with the other Sentry SDKs (#4605)Sentry.Maui.BreadcrumbEventthat had been marked as obsolete. That constructor expected aIEnumerable<(string Key, string Value)>[]argument (i.e. an array of IEnumerable of tuples). If you were using this constructor, you should instead use the alternate constructor that expects just an IEnumerable of tuples:IEnumerable<(string Key, string Value)>.SentrySdk.CaptureUserFeedbackand all associated members. Use the newerSentrySdk.CaptureFeedbackinstead.Features
Sentry.Extensions.AIwhich allows LLM usage instrumentation viaMicrosoft.Extensions.AI(#4657)Sentry.Google.Cloud.Functions(#4700)IsSessionActiveto allow checking the session state (#4662)Unhandledwhen capturing an unhandled but non-terminal exception, i.e. through the UnobservedTaskExceptionIntegration (#4633, #4653)app_memorythat can hold the amount of memory used by the application in bytes. (#4707)PropagateTraceparent = truewhen initializing the SDK if to include the W3C traceparent header on outgoing requests.Fixes
Serilogintegration captures Structured Logs (when enabled) independently of captured Events and added Breadcrumbs (#4691)Sentry.Extensions.Logging,Sentry.AspNetCore,Sentry.MauiandSentry.Google.Cloud.Functionsappsettings.json)SentryLoggingOptions.MinimumBreadcrumbLevel,SentryLoggingOptions.MinimumEventLevel, or add filter functions viaSentryLoggingOptionsExtensions.AddLogEntryFilterappsettings.json)SentryOptions.EnableLogs/NODEFAULTLIB:MSVCRTto NativeAOT linker arguments on Windows when targetting non-Windows platforms (Android, Browser) (#4760)... (truncated)
6.0.0-rc.2
Fixes
Dependencies
6.0.0-rc.1
BREAKING CHANGES
This release adds support for .NET 10 and drops support for net8.0-android, net8.0-ios, net8.0-maccatalyst and net8.0-windows10.0.19041.0 (#4461)
Backpressure handling is now enabled by default, meaning that the SDK will monitor system health and reduce the sampling rate of events and transactions when the system is under load. When the system is determined to be healthy again, the sampling rates are returned to their original levels. (#4615)
QOL improvement: Spans and Transactions now implement
IDisposableso that they can be used withusingstatements/declarations that will automatically finish the span with a status of OK when it passes out of scope, if it has not already been finished, to be consistent withActivityclasses when using OpenTelemetry (#4627)Add support for W3C traceparent header for outgoing requests (#4661)
This feature is disabled by default. Set
PropagateTraceparent = truewhen initializing the SDK if to include the W3C traceparent header on outgoing requests.The Structured Logs APIs are now stable: removed
ExperimentalfromSentryOptions(#4699)Added support for v3 of the Android AssemblyStore format that is used in .NET 10 and dropped support for v1 that was used in .NET 8 (#4583)
CaptureFeedback now returns a
SentryIdand aCaptureFeedbackResultout parameter that indicate whether feedback was captured successfully and what the reason for failure was otherwise (#4613)Deprecated
Sentry.Azure.Functions.Workeras very few people were using it and the functionality can easily be replaced with OpenTelemetry. We've replaced our integration with a sample showing how to do this using our OpenTelemetry package instead. (#4693)UWP support has been dropped. Future efforts will likely focus on WinUI 3, in line with Microsoft's recommendations for building Windows UI apps. (#4686)
BreadcrumbLevel.Criticalhas been renamed toBreadcrumbLevel.Fatalfor consistency with the other Sentry SDKs (#4605)SentryOptions.IsEnvironmentUser now defaults to false on MAUI. The means the User.Name will no longer be set, by default, to the name of the device (#4606)
Remove unnecessary files from SentryCocoaFramework before packing (#4602)
Removed obsolete APIs (#4619)
Sentry.Maui.BreadcrumbEventthat had been marked as obsolete. That constructor expected aIEnumerable<(string Key, string Value)>[]argument (i.e. an array of IEnumerable of tuples). If you were using this constructor, you should instead use the alternate constructor that expects just an IEnumerable of tuples:IEnumerable<(string Key, string Value)>.SentrySdk.CaptureUserFeedbackand all associated members. Use the newerSentrySdk.CaptureFeedbackinstead.SpanTracer and TransactionTracer are still public but these are now
sealed(see also #4627)ScopeExtensions.Populate is now internal (#4611)
See https://develop.sentry.dev/sdk/telemetry/traces/distributed-tracing/#w3c-trace-context-header for more details.
Features
IsSessionActiveto allow checking the session state (#4662)Unhandledwhen capturing an unhandled but non-terminal exception, i.e. through the UnobservedTaskExceptionIntegration (#4633, #4653)app_memorythat can hold the amount of memory used by the application in bytes. (#4707)Fixes
Serilogintegration captures Structured Logs (when enabled) independently of captured Events and added Breadcrumbs (#4691)Dependencies
... (truncated)
6.0.0-preview.2
BREAKING CHANGES
BreadcrumbLevel.Criticalhas been renamed toBreadcrumbLevel.Fatalfor consistency with the other Sentry SDKs (#4605)SentryOptions.IsEnvironmentUser now defaults to false on MAUI. The means the User.Name will no longer be set, by default, to the name of the device (#4606)
Remove unnecessary files from SentryCocoaFramework before packing (#4602)
Removed obsolete APIs (#4619)
Sentry.Maui.BreadcrumbEventthat had been marked as obsolete. That constructor expected aIEnumerable<(string Key, string Value)>[]argument (i.e. an array of IEnumerable of tuples). If you were using this constructor, you should instead use the alternate constructor that expects just an IEnumerable of tuples:IEnumerable<(string Key, string Value)>.SentrySdk.CaptureUserFeedbackand all associated members. Use the newerSentrySdk.CaptureFeedbackinstead.Backpressure handling is now enabled by default, meaning that the SDK will monitor system health and reduce the sampling rate of events and transactions when the system is under load. When the system is determined to be healthy again, the sampling rates are returned to their original levels. (#4615)
ScopeExtensions.Populate is now internal (#4611)
Add support for W3C traceparent header for outgoing requests (#4661)
This feature is disabled by default. When enabled, outgoing requests will include the W3C traceparent header.
See https://develop.sentry.dev/sdk/telemetry/traces/distributed-tracing/#w3c-trace-context-header for more details.
Fixes
6.0.0-preview.1
BREAKING CHANGES
5.16.3
Fixes
Dependencies
5.16.2
Fixes
sentry.proguard-uuidmetadata to be set in Android manifest (#4647)Dependencies
5.16.1
Fixes
sentry.originattribute to so it's clearer where these come from (#4566)Dependencies
5.16.0
Features
EnableBackpressureHandlingoption for Automatic backpressure handling. When enabled this automatically reduces the sample rate when the SDK detects events being dropped. (#4452)Serilog(#4462)Fixes
API Changes
ExperimentalAttributefrom all Structured Logs APIs, and removeExperimentalproperty fromSentrySdk, but keepExperimentalproperty onSentryOptions(#4567)Dependencies
5.15.1
Fixes
SentryOptions.Native.SuppressSignalAbortsandSuppressExcBadAccesson iOS (#4521)Dependencies
5.15.1-maxpath.1
Fixes
SentryOptions.Native.SuppressSignalAbortsandSuppressExcBadAccesson iOS (#4521)Dependencies
5.15.0
Features
params(#4451)keynames ofMicrosoft.Extensions.Loggingattributes (#4450)Fixes
IDisposablefromSentryStructuredLogger. Disposal is intended through the owningIHubinstance (#4424)InvalidOperationExceptionpotentially thrown during a race condition, especially in concurrent high-volume logging scenarios (#4428)Dependencies
5.14.1
Fixes
Dependencies
5.14.0
Features
Sentry.Extensions.Logging,Sentry.AspNetCoreandSentry.Maui(#4193)Fixes
sample_rateof Dynamic Sampling Context (DSC) when making sampling decisions ([#4374](https://github.com/getsentry/sentry-dotnet/...Description has been truncated