Repository navigation
chore(deps): Bump AWSSDK.S3 and 14 others - #81
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps AWSSDK.S3 from 4.0.104.11 to 4.1.1 Bumps coverlet.collector from 10.1.0 to 10.1.1 Bumps Fido2 from 4.3.2 to 4.3.3 Bumps JasperFx.Events from 2.101.0 to 2.102.0 Bumps JasperFx.Events.SourceGenerator from 2.101.0 to 2.102.0 Bumps Marten from 9.58.0 to 9.62.0 Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.14 to 10.0.15 Bumps Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15 Bumps Microsoft.Data.SqlClient from 6.1.1 to 6.1.8 Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0 Bumps Scalar.AspNetCore from 2.19.0 to 2.21.0 Bumps System.Security.Cryptography.Pkcs from 10.0.13 to 10.0.15 Bumps WolverineFx.Http from 6.63.0 to 6.64.2 Bumps WolverineFx.Marten from 6.63.0 to 6.64.2 Bumps WolverineFx.RuntimeCompilation from 6.63.0 to 6.64.2 --- updated-dependencies: - dependency-name: AWSSDK.S3 dependency-version: 4.1.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: Fido2 dependency-version: 4.3.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: JasperFx.Events dependency-version: 2.102.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: JasperFx.Events.SourceGenerator dependency-version: 2.102.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: Marten dependency-version: 9.62.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: Microsoft.Data.SqlClient dependency-version: 6.1.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: Scalar.AspNetCore dependency-version: 2.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-menores - dependency-name: WolverineFx.Http dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: WolverineFx.Marten dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.64.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-menores ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Nov 18, 2026
Contributor
Author
|
Superseded by #84. |
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.
Pinned AWSSDK.S3 at 4.1.1.
Release notes
Sourced from AWSSDK.S3's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated coverlet.collector from 10.1.0 to 10.1.1.
Release notes
Sourced from coverlet.collector's releases.
10.1.1
Improvements
IsReachableto branch points, computed from the method's control-flow graph, and exclude unreachable branches from branch-coverage totals and from branch details in Cobertura, LCOV and OpenCover reports #2056 by @pcshrosbreeFixed
Maintenance
Diff between 10.1.0 and 10.1.1
Commits viewable in compare view.
Pinned Fido2 at 4.3.3.
Release notes
Sourced from Fido2's releases.
4.3.3
What's Changed
Full Changelog: passwordless-lib/fido2-net-lib@4.3.2...4.3.3
Commits viewable in compare view.
Pinned JasperFx.Events at 2.102.0.
Release notes
Sourced from JasperFx.Events's releases.
2.102.0
JasperFx 2.102.0 is a minor release with one new
IEventDatabasecapability. It lets monitoring report projection lag as time rather than as a count of events.IEventDatabase.FetchFirstEventTimestampsAfterAsync, the age of the oldest unprocessed event (#1150 / #1151).(TenantId, Sequence)position, it returns the store's timestamp of the first event with a higher sequence, ornullwhen there is none (the shard is caught up). You get onePendingEventAge(TenantId, Sequence, Timestamp)per position, in the order asked.PendingEventAgealso hasIsCaughtUpandAgeAt(now), which never returns a negative age when clocks are skewed.NotSupportedExceptionon a store that hasn't implemented it. Anulltimestamp means "caught up", so that default can't answer without reporting a lagging shard as current. The single-position convenienceFetchFirstEventTimestampAfterAsync(sequence, tenantId)calls the batched member by default. The in-memory prototyping store implements both.PendingEventAgeCompliancesuite, gated bySupportsPendingEventAges(default false), with 12 facts. They cover the "strictly after" rule, ordering and duplicates, archived events and conjoined tenant scoping. A newSupportsStreamArchivingfixture flag (default true) gates the archived facts. Stores must enroll the new suite (or excuse it) orComplianceSuiteInventory.AssertEnrolledfails.Marten, Polecat and Fisher implement the method in their JasperFx 2.102.0 upgrades.
What's Changed
Full Changelog: JasperFx/jasperfx@v2.101.1...v2.102.0
2.101.1
JasperFx 2.101.1 is a patch release with one fix.
StopAsync/PauseAsynccalls on the projection coordinator no longer throwObjectDisposedException(#1148 / #1149).ProjectionCoordinatorBaseread, awaited across, then disposed and replaced its shared cancellation source and runner with nothing serializing callers. Two stops in flight at once could cancel a source the other had just disposed. Two starts in flight at once could each build a leadership loop, leaving one running that nothing would ever cancel.RunCommandstops the host again whenApplicationStoppingfires, so tests hosting an app throughWebApplicationFactoryor Alba had twoIHost.StopAsynccalls racing at teardown.ProjectionCoordinatorpick this up from the base class. Marten'sExplicitProjectionCoordinatorhas its own fix in JasperFx/marten#5843.StressTestsproject that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.What's Changed
Full Changelog: JasperFx/jasperfx@v2.101.0...v2.101.1
Commits viewable in compare view.
Updated JasperFx.Events.SourceGenerator from 2.101.0 to 2.102.0.
Release notes
Sourced from JasperFx.Events.SourceGenerator's releases.
2.102.0
JasperFx 2.102.0 is a minor release with one new
IEventDatabasecapability. It lets monitoring report projection lag as time rather than as a count of events.IEventDatabase.FetchFirstEventTimestampsAfterAsync, the age of the oldest unprocessed event (#1150 / #1151).(TenantId, Sequence)position, it returns the store's timestamp of the first event with a higher sequence, ornullwhen there is none (the shard is caught up). You get onePendingEventAge(TenantId, Sequence, Timestamp)per position, in the order asked.PendingEventAgealso hasIsCaughtUpandAgeAt(now), which never returns a negative age when clocks are skewed.NotSupportedExceptionon a store that hasn't implemented it. Anulltimestamp means "caught up", so that default can't answer without reporting a lagging shard as current. The single-position convenienceFetchFirstEventTimestampAfterAsync(sequence, tenantId)calls the batched member by default. The in-memory prototyping store implements both.PendingEventAgeCompliancesuite, gated bySupportsPendingEventAges(default false), with 12 facts. They cover the "strictly after" rule, ordering and duplicates, archived events and conjoined tenant scoping. A newSupportsStreamArchivingfixture flag (default true) gates the archived facts. Stores must enroll the new suite (or excuse it) orComplianceSuiteInventory.AssertEnrolledfails.Marten, Polecat and Fisher implement the method in their JasperFx 2.102.0 upgrades.
What's Changed
Full Changelog: JasperFx/jasperfx@v2.101.1...v2.102.0
2.101.1
JasperFx 2.101.1 is a patch release with one fix.
StopAsync/PauseAsynccalls on the projection coordinator no longer throwObjectDisposedException(#1148 / #1149).ProjectionCoordinatorBaseread, awaited across, then disposed and replaced its shared cancellation source and runner with nothing serializing callers. Two stops in flight at once could cancel a source the other had just disposed. Two starts in flight at once could each build a leadership loop, leaving one running that nothing would ever cancel.RunCommandstops the host again whenApplicationStoppingfires, so tests hosting an app throughWebApplicationFactoryor Alba had twoIHost.StopAsynccalls racing at teardown.ProjectionCoordinatorpick this up from the base class. Marten'sExplicitProjectionCoordinatorhas its own fix in JasperFx/marten#5843.StressTestsproject that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.What's Changed
Full Changelog: JasperFx/jasperfx@v2.101.0...v2.101.1
Commits viewable in compare view.
Pinned Marten at 9.62.0.
Release notes
Sourced from Marten's releases.
9.62.0
Marten 9.62.0 is a small bug-fix release on Weasel 9.51.0.
Fixes
SetFloor()can no longer be undone by an id fetch already in progress (#5998). Before this release, aNextLong()that had already reserved its next block could finish installing it afterSetFloor(n)returned. That handed out ids below the new floor, and under the same race an id could also be issued twice.SetFloor()now waits for that fetch and installs its own block after it. The fix is in Weasel 9.51.0 (weasel#849, weasel#853); there's no Marten code change.GetTenant()for an uncached tenant now checks for the tenant's database, and runsCREATE DATABASEwhen it's missing, with synchronous I/O on the calling thread. It used to block on the async path. The exception is aMultiplexingmaster connection, which Npgsql only supports asynchronously. Together with 9.61.0, all three per-tenant database tenancies (master table, single instance, sharded) now resolve known tenants without sync-over-async.No schema changes. Weasel goes from 9.50.0 to 9.51.0 (additive). JasperFx stays at 2.102.0.
What's Changed
Full Changelog: JasperFx/marten@V9.61.0...V9.62.0
9.61.0
Marten 9.61.0 is a bug-fix release for multi-tenancy. Its two themes are synchronous tenant resolution under load and sharded tenant assignments.
Behaviour change (see the migration guide, "Key Changes in 9.61.0", on the
9.0branch)Marten.Exceptions.AssignedShardNotFoundException(TenantId,DatabaseId) and doesn't reassign the tenant.Fixes
ForTenant(tenantId)resolve a tenant that isn't cached yet. They used to do that with sync-over-async, so a burst of first sessions for new tenants could stall the whole process. That burst is typical right after a deploy.Multiplexingcontrol database, which Npgsql only supports asynchronously.GetTenantAsync()before its first synchronous session.Repository and test-only
Disposetolerates a half-built context (#5976), and a MultiHostTests standby-replay fix (#5979).tests.ymland the docs checks on pull requests and pushes to9.0(#5977).No schema changes and no dependency changes: JasperFx 2.102.0 and Weasel 9.50.0, as in 9.60.0.
What's Changed
Full Changelog: JasperFx/marten@V9.60.0...V9.61.0
9.60.0
Marten 9.60.0 is a bug-fix release, mostly for LINQ correctness. Several queries that silently returned wrong results now return what LINQ to Objects returns. Shapes Marten can't translate exactly now throw
BadLinqExpressionExceptioninstead of returning the wrong rows.Behaviour changes (see the migration guide, "Key Changes in 9.60.0")
Count()afterTake()/Skip()counts the page.Skip(k).Take(n).Count()used to return 0, andTake(n).Count()the full count (#5920).Take()/Skip()beforeSelectMany()pages the parent documents, not the flattened rows (#5928).Select()afterSelectMany()projects the flattened rows. The projection used to be silently dropped (#5933).OrderBy()re-sorts the results, as LINQ does (#5959).OrderBy(x => -x.Number)are computed, including over child documents and joins, or refused. They used to sort by the underlying member (#5957, #5968).OrderBy()after a projection orders the projected values (#5955).OrderBy/Select/jaggedWhere. A negative index now throws (#5949).FetchForWriting()version conflict in the same save as aStartStream()now throwsEventStreamUnexpectedMaxEventIdException(aConcurrencyException) instead of a wrongExistingStreamIdCollisionException(#5914).Schema change
mt_get_next_hiis now an atomic increment (#5938). Under concurrent load, HiLo could use up its retry limit and throwHiloSequenceAdvanceToNextHiAttemptsExceededException. The function body changes, so your next schema migration applies it. Until then the old function keeps working.Other fixes
ReadSessionPreference, so a lagging standby can no longer make it skip events (#5888).BeginTransactionAsyncis cancelled or fails (#5881).Store()calls no longer stalls the process through thread-pool starvation (#5969).First/SingleafterSelectMany(#5921)Any()over aGroupJoinSelectManyover duplicated arrays (#5934) and enum arrays (#5940)LengthafterSelectMany(#5941)Select()(#5942)What's Changed
... (truncated)
9.59.0
Marten 9.59.0 moves to JasperFx 2.102.0 and Weasel 9.50.0. It adds read-only DCB tag queries on a query session, reports how old a projection's oldest unprocessed event is, and fixes a shutdown race in the explicit projection coordinator.
Highlights
EventsExistAsync,QueryByTagsAsyncandAggregateByTagsAsyncare now onIQuerySession.Events, so a read-only endpoint no longer needs a document session to read by tags (thanks to new contributor @alekbarszczewski, #5841).FetchForWritingByTagsstill needs a document session. Existing calls throughIDocumentSession.Eventsare unchanged, both in source and in compiled assemblies. A class that implementsMarten.Events.IQueryEventStoreitself has three more members to implement.IEventDatabase.FetchFirstEventTimestampsAfterAsync. It returns the timestamp of the oldest event a shard hasn't processed yet, in one round trip. CritterWatch uses it to report projection lag as time instead of a count of events (#5844).StopAsync/PauseAsynccalls, such as the second stop JasperFx'sRunCommandissues whenWebApplicationFactoryor Alba stops the host, no longer stop and dispose the same daemons twice or log "Error while trying to stop daemon agents". A start that overlaps a stop no longer starts a disposed daemon, and a daemon resolved during a stop is no longer dropped without being disposed (#5842, #5843).db-*commands (db-apply,db-assert,db-patch,db-dump,db-list) now appear and run there too. JIT applications see no change (#5840, #5845).AutoCreate, apply at startup,db-apply/resources setupas a deployment step, ordb-patchscripts for a DBA, with links to the Weasel CLI and JasperFx stateful resource docs (#5839).What's Changed
New Contributors
Full Changelog: JasperFx/marten@v9.58.0...V9.59.0
Commits viewable in compare view.
Pinned Microsoft.AspNetCore.Authentication.JwtBearer at 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.OpenApi's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Data.SqlClient from 6.1.1 to 6.1.8.
Release notes
Sourced from Microsoft.Data.SqlClient's releases.
6.1.8
This update brings the following changes since the 6.1.7 release:
Changed
Updated the
System.Security.Cryptography.Pkcsdependency to 8.0.2 (was 8.0.1) for .NET Framework 4.6.2, .NET 8.0, and .NET Standard 2.0, and updated theMicrosoft.Extensions.Caching.Memory,System.Configuration.ConfigurationManager, andSystem.Security.Cryptography.Pkcsdependencies to 9.0.21 (was 9.0.11) for .NET 9.0.(#4842, #4862, #4870)
Improved the error reported when
Active Directory Interactiveauthentication through the Windows Web Account Manager (WAM) broker fails because the host has no parent window, such as a service or Azure Functions host. The resulting error now explains the supported alternatives: supply a parent window withSetParentActivityOrWindowFunc, useActive Directory Defaultwith a configured non-interactive credential, or supply a customApplicationClientIdwithUseWamBrokerdisabled. The original MSAL error code and inner exception are preserved, and authentication selection, retry behavior, and other failures are unchanged. (Windows only)(#4854, #4858, #4918)
Fixed
Fixed the managed SNI path ignoring
HostNameInCertificateduring server certificate validation. WhenHostNameInCertificateis set, it is now the only host name the server certificate is validated against, and certificates that do not match it are rejected. Default host-name selection when the property is not set, certificate chain validation,ServerCertificatematching, and the connection destination are unchanged. (net8.0/net9.0 only)(#4905, #4909)
Fixed Always Encrypted enclave session caching so that cached enclave sessions are isolated by attestation protocol. A session established with one
Attestation Protocolsetting is no longer reused by a connection to the same server, database, and attestation URL that uses a different protocol.(#4829, #4868)
Fixed
SqlDataReader.HasRowsreturningfalsewhen a result set contains rows but the server sends multiple informational messages, or an informational message before anORDERtoken, ahead of the first row. Empty results still reportfalse, andInfoMessagedelivery is unchanged.(#3018, #4773, #4898)
Fixed an intermittent
InvalidOperationException("Nullable object must have a value") from statistics bookkeeping when commands complete concurrently on a MARS connection. This issue was reported as a regression starting with 6.1.4.(#4778, #4875, #4896)
Fixed Entra ID authentication when the server supplies an authority URL with an OAuth endpoint suffix, such as
https://login.microsoftonline.com/<tenant>/oauth2/authorizereturned by the Dataverse/Dynamics 365 TDS endpoint. The provider now extracts the tenant from the first path segment and uses the normalized authority for Azure.Identity credentials, MSAL, and their cache keys. An authority URL that cannot be parsed now fails with a clear, localizedArgumentExceptionnaming the authority. Bare tenant authority URLs used by Azure SQL and Fabric retain their existing behavior.(#4496, #4521, #4791, #4807)
Target Platform Support
Full details: release-notes/6.1/6.1.8.md
6.1.7
This update brings the following changes since the 6.1.6 release:
Changed
Microsoft.Data.SqlClient.SNIandMicrosoft.Data.SqlClient.SNI.runtimedependencies to 6.0.3 (was 6.0.2).(#4598)
Fixed
Fixed
ServerCertificatevalidation on the managed SNI path so the configured certificate is compared against the server certificate even when the server certificate passes chain and host-name validation. When certificate validation is enabled, a missing, unreadable, or invalid certificate file, a certificate mismatch, or a missing server certificate now causes the TLS handshake to fail instead of bypassing the configured certificate check. (net8.0/net9.0 only)(#4445, #4584)
Fixed Always Encrypted VSM/HGS enclave attestation to verify that the enclave public key used to establish a session matches the key committed to by the signed attestation report. Missing, malformed, or mismatched key-binding data now causes attestation to fail before the session secret is derived.
(#4532, #4552)
Fixed
SqlConnection.AccessTokenCallbacknot disabling Transparent Network IP Resolution by default, making it consistent withSqlConnection.AccessToken. An explicitly configuredTransparentNetworkIPResolutionconnection-string value still takes precedence. (net462 only)(#4520, #4560)
Fixed token authentication state handling so clearing
SqlConnection.AccessTokenpreserves an existingAccessTokenCallbackin the connection pool key, and clearingAccessTokenCallbackpreserves an existingAccessToken. Callback-based authentication now also follows the same prelogin server-certificate validation rules as an explicitly supplied access token.(#4520, #4560)
Fixed configurable retry logic installing a permanent, process-wide assembly-resolution handler that could interfere with unrelated assembly loading. The handler is now active only while an explicitly configured custom retry provider is resolved and constructed, and probes
AppContext.BaseDirectoryinstead of the current working directory. Place custom retry assemblies in the application base directory; dependencies loaded after provider construction must be resolvable through normal application dependency resolution or an application-provided handler. (net8.0/net9.0 only)(#2214, #4547, #4664)
Target Platform Support
Full details: release-notes/6.1/6.1.7.md
6.1.6
This update brings the following changes since the 6.1.5 release:
Added
WAM broker support for the supported Entra ID authentication modes (Windows only)
What Changed:
ActiveDirectoryAuthenticationProviderOptionsoptions bag and a correspondingActiveDirectoryAuthenticationProvider(ActiveDirectoryAuthenticationProviderOptions options)constructor were introduced, exposing aUseWamBrokerproperty (alongsideApplicationClientIdandDeviceCodeFlowCallback).(#4288, #4387)
SetParentActivityOrWindowFunc(Func<object> parentActivityOrWindowFunc)method so callers can supply a parent window handle on Windows or a parentActivity/UIViewControlleron Android/iOS/MAUI.Who Benefits:
ActiveDirectoryInteractiveand other supported Entra ID authentication modes on Windows benefit from the WAM broker's improved security (tokens are brokered by the OS), single sign-on with the logged-in Windows account, and support for Conditional Access and Windows Hello.Impact:
ApplicationClientId, WAM is opt-in viaActiveDirectoryAuthenticationProviderOptions.UseWamBroker. Consider enabling it when you want OS-brokered tokens, single sign-on with the signed-in Windows account, Windows Hello, and Conditional Access support.UseWamBrokeris a Windows-only setting and has no effect on non-Windows platforms, where interactive Entra ID flows always use the system browser.Changed
Hardened TDS token parsing with data-length bounds checks
What Changed:
(#4340, #4359)
Who Benefits:
Impact:
... (truncated)
6.1.5
This update brings the following changes since the 6.1.4 release:
Fixed
ExecuteScalarto properly propagate errors when the server sends data followed by an error token. Previously, errors such as conversion failures duringWHEREclause evaluation were silently consumed duringSqlDataReader.Close()instead of being thrown to the caller, which could result in transactions being unexpectedly zombied. (#3736, #3947)SqlDataReader.GetFieldTypeandSqlDataReader.GetProviderSpecificFieldTypeto return the correct type (SqlVector<float>) for vector float32 columns. Previously, these methods did not follow the same type-resolution logic asGetValue, returning an incorrect type for vector columns. (#4104, #4151)Target Platform Support
Dependencies
.NET Framework 4.6.2
.NET 8.0
.NET 9.0
... (truncated)
6.1.4
This update brings the following changes since the 6.1.3 release:
Fixed
SqlDataAdapterwhen processing batch scenarios where certain SQL RPC calls may not include system parameters.(#3877)
(#3776)
Added
AppContext Switch for enabling MultiSubnetFailover
What Changed:
Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefaultto setMultiSubnetFailover=trueby default in connection string.(#3851)
Who Benefits:
Impact:
Changed
SqlStatisticsexecution timing by usingEnvironment.TickCountinstead of more expensive timing mechanisms.... (truncated)
6.1.3
This update includes the following changes since the 6.1.2 release:
Added
App Context Switch for Ignoring Server-Provided Failover Partner
What Changed:
Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartnerwas introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR #3702.Who Benefits:
Impact:
tcp:host,port) so that the client uses that instead of the server's suggestion.Fixed
Target Platform Support
Dependencies
.NET Framework 4.6.2+
... (truncated)
6.1.2
This update brings the below changes over the previous stable release:
Fixed
System.InvalidOperationException#3629Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.12.0
Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
18.11.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
Commits viewable in compare view.
Updated Scalar.AspNetCore from 2.19.0 to 2.21.0.
Release notes
Sourced from Scalar.AspNetCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated System.Security.Cryptography.Pkcs from 10.0.13 to 10.0.15.
Release notes
Sourced from System.Security.Cryptography.Pkcs's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned WolverineFx.Http at 6.64.2.
Release notes
Sourced from WolverineFx.Http's releases.
6.64.2
Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the
6.0branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.Fixes
[DeduplicatedWithResponse]now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @esond (#5563).Request.Formread. #5562 builds on this. Thanks to @uniquelau.Known 6.x behavior, unchanged: with
UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.Full change list: #5575.
6.64.1
Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the
6.0branch). It backports four bug fixes from 7.0 and adds no public API.Fixes
codegen-preview,describe-routinganddescribecommands no longer fail on an application that has a recurring schedule.6.0through #5566): MySQL node-record housekeeping no longer deadlocks.Build and CI
6.0branch, so 6.x releases are gated likemain.Microsoft.DotNet.ILCompiler. The pin conflicted with the .NET 11 SDK's runtime pack (a backport of the fix onmain).Not included: #5562 (
[DeduplicatedWithResponse]with multipart and form bodies). It depends on 7.0's async form-read rework.Full change list: #5571.
6.64.0
A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.
Fixes
NativeAckendpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).IWolverineObserver.CircuitBreakerResetis now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened onCircuitBreakerTrippedcould never be closed by Wolverine's own signal. A new overload,CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own afterPauseTimeor through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).ResetResourceState()no longer adds a newwolverine.response.*queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, soInvokeAsync<T>()timed out (GH-5452, thanks to @alesdvorakcz).Docs
AutoCreate(#5445).What's Changed
ResetResourceState()calls by @alesdvorakcz in GH-5452: Rabbit MQ keeps one reply queue acrossResetResourceState()calls JasperFx/wolverine#5453Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0
Commits viewable in compare view.
Pinned WolverineFx.Marten at 6.64.2.
Release notes
Sourced from WolverineFx.Marten's releases.
6.64.2
Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the
6.0branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.Fixes
[DeduplicatedWithResponse]now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @esond (#5563).Request.Formread. #5562 builds on this. Thanks to @uniquelau.Known 6.x behavior, unchanged: with
UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.Full change list: #5575.
6.64.1
Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the
6.0branch). It backports four bug fixes from 7.0 and adds no public API.Fixes
codegen-preview,describe-routinganddescribecommands no longer fail on an application that has a recurring schedule.6.0through #5566): MySQL node-record housekeeping no longer deadlocks.Build and CI
6.0branch, so 6.x releases are gated likemain.Microsoft.DotNet.ILCompiler. The pin conflicted with the .NET 11 SDK's runtime pack (a backport of the fix onmain).Not included: #5562 (
[DeduplicatedWithResponse]with multipart and form bodies). It depends on 7.0's async form-read rework.Full change list: #5571.
6.64.0
A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.
Fixes
NativeAckendpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).IWolverineObserver.CircuitBreakerResetis now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened onCircuitBreakerTrippedcould never be closed by Wolverine's own signal. A new overload,CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own afterPauseTimeor through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).ResetResourceState()no longer adds a newwolverine.response.*queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, soInvokeAsync<T>()timed out (GH-5452, thanks to @alesdvorakcz).Docs
AutoCreate(#5445).What's Changed
ResetResourceState()calls by @alesdvorakcz in GH-5452: Rabbit MQ keeps one reply queue acrossResetResourceState()calls JasperFx/wolverine#5453Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0
Commits viewable in compare view.
Updated WolverineFx.RuntimeCompilation from 6.63.0 to 6.64.2.
Release notes
Sourced from WolverineFx.RuntimeCompilation's releases.
6.64.2
Wolverine 6.64.2 is a patch release on the 6.x maintenance line (the
6.0branch). It backports two Wolverine.HTTP fixes from 7.0 and adds no public API.Fixes
[DeduplicatedWithResponse]now works with multipart uploads and form posts. A retried upload or form post gets the first response again, where it used to get a 422. An endpoint that binds a form value is no longer refused. A form that ASP.NET Core reads before the endpoint (an antiforgery token sent as a form field) is fingerprinted too, and the antiforgery token is left out of the fingerprint, because a browser that reloads the page gets a new token for the same request. Thanks to @esond (#5563).Request.Formread. #5562 builds on this. Thanks to @uniquelau.Known 6.x behavior, unchanged: with
UseAntiforgery(), a form post with no token answers 500 rather than 400, because ASP.NET Core throws when the endpoint reads a form that failed antiforgery validation. 7.0 answers 400 through its in-endpoint antiforgery check (GH-5147), which is not backported.Full change list: #5575.
6.64.1
Wolverine 6.64.1 is a patch release on the 6.x maintenance line (the
6.0branch). It b...Description has been truncated