Repository navigation
Bump FsCheck.Xunit.v3 and 11 others - #116
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps FsCheck.Xunit.v3 from 3.4.0 to 3.6.0 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.12 to 10.0.15 Bumps Microsoft.Data.SqlClient to 7.1.2 Bumps Microsoft.Extensions.DependencyInjection to 11.0.0 Bumps Microsoft.Extensions.Diagnostics from 10.0.14 to 11.0.0 Bumps Microsoft.Extensions.Diagnostics.Testing from 10.10.0 to 11.0.0 Bumps Microsoft.Extensions.Logging from 10.0.14 to 11.0.0 Bumps Microsoft.Extensions.TimeProvider.Testing from 10.10.0 to 11.0.0 Bumps Microsoft.Testing.Extensions.CodeCoverage from 18.11.2 to 18.12.0 Bumps Testcontainers.MsSql from 4.15.0 to 4.17.0 Bumps Testcontainers.PostgreSql from 4.15.0 to 4.17.0 Bumps xunit.v3 from 4.0.1 to 4.0.3 --- updated-dependencies: - dependency-name: FsCheck.Xunit.v3 dependency-version: 3.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: everything-else - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: everything-else - dependency-name: Microsoft.Data.SqlClient dependency-version: 7.1.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: everything-else - dependency-name: Microsoft.Data.SqlClient dependency-version: 7.1.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: everything-else - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: everything-else - dependency-name: Microsoft.Extensions.DependencyInjection dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: everything-else - dependency-name: Microsoft.Extensions.Diagnostics dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: everything-else - dependency-name: Microsoft.Extensions.Diagnostics.Testing dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: everything-else - dependency-name: Microsoft.Extensions.Logging dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: everything-else - dependency-name: Microsoft.Extensions.TimeProvider.Testing dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: everything-else - dependency-name: Microsoft.Testing.Extensions.CodeCoverage dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: everything-else - dependency-name: Testcontainers.MsSql dependency-version: 4.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: everything-else - dependency-name: Testcontainers.PostgreSql dependency-version: 4.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: everything-else - dependency-name: xunit.v3 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: everything-else ... Signed-off-by: dependabot[bot] <support@github.com>
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.
Updated FsCheck.Xunit.v3 from 3.4.0 to 3.6.0.
Release notes
Sourced from FsCheck.Xunit.v3's releases.
3.6.0
Additionally target netstandard2.1 and net8.0.
Added generators and shrinkers for
System.IndexandSystem.Range(#621),Memory<T>,ReadOnlyMemory<T>,ReadOnlySequence<T>,ValueTaskandValueTask<T>in netstandard2.1.Added generators and shrinkers for
System.Half,Int128,UInt128,DateOnly,TimeOnlyandRunein net8.0.Added
NullableRef<T>to conveniently generate nulls for reference types (#610).3.5.0
Support NUnit 5 (by Nathan Bierema)
Added support for NUnit ValueFormatters.
Added
Gen.delayto defer generator construction until a value is generated.Added support for timeout in xUnit v3.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.12 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned Microsoft.Data.SqlClient at 7.1.2.
Release notes
Sourced from Microsoft.Data.SqlClient's releases.
7.1.2
This servicing release includes security updates, certificate and enclave-session validation fixes, and improvements to result reading and managed networking.
Use matching
7.1.2versions of the driver and companion packages. Assemblies retainAssemblyVersion 7.0.0.0; no new .NET Framework binding redirects are required when upgrading from7.1.1.Microsoft.SqlServer.Serveris unchanged and versioned independently.Changes Since 7.1.1
Changed
System.Security.Cryptography.Pkcs8.0.2 for net462/net8.0/netstandard2.0 and affected .NET 9 dependencies, includingSystem.Threading.RateLimiting, to 9.0.21.Fixed
HostNameInCertificateduring managed SNI certificate validation, even when the certificate matches the server name (net8.0/net9.0). (#4907)SqlDataReader.HasRowsreturningfalsewhen informational messages precede the first row. (#4900)GetTextReaderreads corruptingnvarchartext on big-endian platforms. (#4961)IndexOutOfRangeException. (#4977)TypeInitializationExceptionorDllNotFoundExceptionon Unix (net8.0/net9.0). (#4770)Companion Packages
All packages below ship as
7.1.2.window_handle_requirederrors, preserving the original error code and inner exception.For Windows WAM errors, provide a parent window through
SetParentActivityOrWindowFunc, or useAuthentication=Active Directory Defaultwith a configured non-interactive credential in windowless hosts. Interactive authentication without WAM requires a customApplicationClientIdandUseWamBroker=false. WAM remains enforced for SqlClient's first-party application ID; no automatic fallback was added.Platform Support
.NET Framework 4.6.2+ on Windows and .NET 8.0+ on Windows, Linux, and macOS. Companion package targets and dependency lists are included in the linked package notes.
Thanks to LaurensVergote and shreyarao4 for contributing.
Full release notes and dependency versions
7.1.1
This servicing release fixes decimal parameter validation, token expiry handling in connection pool V2, and connection opens that are in progress when a pool is cleared.
Companion package release notes
Changes Since 7.1.0
Fixed
Fixed an
ArgumentExceptionwhen sending zero-valueddecimalorSqlDecimalparameters whose precision equals their scale. Nonzero precision validation and support for large decimal values are unchanged. (#4715, #4721, #4732)Fixed connection pool V2 handing out pooled connections with expired or nearly expired access tokens. The pool now checks token expiry before reuse, matching the default pool's behavior while preserving transaction-affine reuse. This affects only applications that opt in to connection pool V2. (#4734, #4739)
Fixed connection opens failing when
ClearPoolorClearAllPoolsraces with an in-flight open. Requests already admitted to the cleared pool can finish, and connections returned to the retired pool are discarded rather than reused. (#4714, #4718, #4740)Target Platform Support
Dependencies
.NET 9.0
... (truncated)
7.1.0
This is the general availability release of Microsoft.Data.SqlClient 7.1. It closes out the
7.1preview cycle with application identity reporting for telemetry, the deprecation ofTransparentNetworkIPResolution, and a set of connection, transaction, and Named Pipes fixes.Companion package release notes
Changes Since 7.1.0-preview3
Added
Application Identity in the USERAGENT Payload
What Changed:
RegisteredApplicationenum and a matchingSqlConnection.RegisteredApplicationproperty that let a library or tool identify itself to SQL Server through version 2 of the TDS USERAGENT feature extension. The payload also carries a new driver-owned 64-bit Driver Properties flag field; bit 0 reports whether connection pool V2 is enabled for the process. Both fields are emitted as unpadded uppercase hexadecimal. (#3201, #4632)Who Benefits:
Impact:
RegisteredApplicationis unset reportsUnknown(0). On the wire the field itself is new — USERAGENT payload v1 carried no application identifier, while v2 always emits one.OpenorOpenAsync. Assigning it while the connection is connecting or open throwsInvalidOperationException.ushort-backed and marked[CLSCompliant(false)]. Values are partitioned by range:0x0001–0x7FFFfor Microsoft-defined large-scale applications,0x8000–0xBFFFfor small-scale use, and0xC000–0xFFFFfor public/developer use. Applications that are not yet registered can cast an unassigned value from the appropriate range.... (truncated)
7.1.0-preview3
This update brings the following changes since the 7.1.0-preview2 release.
Packages in this release
Microsoft.Data.SqlClient7.1.0-preview3Added
virtualmethods onSqlColumnEncryptionKeyStoreProviderwithCancellationTokensupport. Purely additive; defaults delegate to the synchronous methods, so existing providers are unaffected (#3672, #3673)Switch.Microsoft.Data.SqlClient.UseConnectionPoolV2):Min Pool Sizeand automatic replenishment (#4452)Connection Idle Timeout(#4463)ConcurrencyLimiterrate limiting for new physical connections (#4395, #4396)number-of-reclaimed-connectionscounter (#4529)Changed
PacketDatanode reuse —ExecuteReaderAsyncgoes from +120.9% to +0.1% against 6.1.6 (#4536)SqlBulkCopyskips graph alias mapping when no graph pseudo-columns are present, recovering a regression from #3677 (#4535)SqlClientEventSourcetracing is disabled, recovering a memory regression against 6.1.6. Trace output unchanged (#4528)net9.0dependencies moved to9.0.18;System.Threading.RateLimitingadded to packaged metadata. Other targets keep their8.0.xpins (#4507)Microsoft.Data.SqlClient.SNIand.SNI.runtimeupdated to7.1.0-preview3.26226.3(#4564)Fixed
SHA-256comparison againstEnclaveData(#4532)SqlConnectionFactoryno longer wakes the process every 30 seconds when no pools exist — including withPooling=Falseand afterClearAllPools()(#1881, #4479)active-soft-connectsandnumber-of-active-connectionscould go negative after a failed activation, and several gauges drifted upward permanently after a broken connection was replaced (#4504)OverflowExceptionwhen sending largedecimalvalues with explicitPrecisionandScale, which primarily affected Always Encrypted (#1655, #4443)DateOnlyvalue withSqlDbType.Variant(net8.0/net9.0) (#3953, #4294)DateOnlyin table-valued parametersql_variantcolumns sent asdatetimeinstead ofdate, which overflowed for values valid asdate(net8.0/net9.0) (#3934, #4439)ServerCertificatekeyword ignored when the platform reported no TLS policy errors. It is now always compared, and an unloadable certificate fails closed withSSLCertificateAuthenticationExceptioninstead of silently falling back to host-name validation (#4445)SqlConnection.AccessTokenCallbacknot disabling TNIR by default, plus pool-key construction andSspiContextProviderexclusivity with token auth (net462 for the TNIR behavior) (#4520)OutOfMemoryExceptioncaptured into faultedTasks across severalSqlBulkCopy,SqlDataReader, andSqlCommandasync entry points (#4437)Microsoft.Data.SqlClient.Extensions.Azure(#4496, #4521)Full details: release-notes/7.1/7.1.0-preview3.md
Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider7.1.0-preview3Added
SqlColumnEncryptionAzureKeyVaultProvideroverrides the four asynchronous key store provider methods introduced in #3673, calling the Azure SDK's own async APIs and flowing the suppliedCancellationToken(#4540)... (truncated)
7.1.0-preview2
This update brings the following changes since the 7.1.0-preview1 release.
Packages in this release
Microsoft.Data.SqlClient7.1.0-preview2Added
SqlConnection.GetSchemaAsyncoverloads withCancellationTokensupport (#3005)$node_id,$edge_id,$from_id,$to_id) accepted inSqlBulkCopymappings (#3677)SqlBatchCommand.CommandBehaviorandSqlBatch.ExecuteReader(CommandBehavior)are now honored (#4125)Connection Idle Timeout/SqlConnectionStringBuilder.IdleTimeout(opt-in viaSwitch.Microsoft.Data.SqlClient.UseLegacyIdleTimeoutBehavior=false) (#4295)Changed
Connect Timeoutnow propagates through the pool whenSwitch.Microsoft.Data.SqlClient.UseOverallConnectTimeoutForPoolWait=trueis set (default off; introduces aMicrosoft.Bcl.TimeProviderdependency) (#4270)jsontype added to theDataTypescollection returned bySqlConnection.GetSchema(#3858)Interlocked.CompareExchangeguards (#4267)SqlErrorCollectionand null-return paths (#4157, #4099, #4102)EnclaveDiffieHellmanInfo.Sizeaccuracy (#4346)SqlVector<float>serialization is now explicitly little-endian for cross-architecture consistency (#3861)10.0.300(#4287)Fixed
NullReferenceExceptioninSqlCommand.Cancel()when the connection has already been torn down (#4372)SqlBulkCopyfailing in least-privilege environments (#4306)CekMdVersion/EkValueCountreads aligned with the TDS specification (#4240)LoginWithFailoverparser-state validation (#4140)Protocol=None/Protocol=Admin(#4180)SqlConnection.TryOpenInnerthat could surface asInvalidCastExceptionnow returns a deterministicInvalidOperationException(#4179)CancellationTokenSourceleaks inSqlDataReader,SqlConnection,SqlCommandreconnect paths, and sequential-stream helpers (#4009)Removed (breaking)
Type System Version=SQL Server 2000now throwsArgumentExceptionat open. Applications should switch toLatest(or another supported value). No change to server-version support — 7.0 / 2000 were already rejected during login version negotiation. (#4015)Full details: release-notes/7.1/7.1.0-preview2.md
Microsoft.Data.SqlClient.Extensions.Azure7.1.0-preview2Added — WAM (Windows Account Manager) broker support for Entra ID authentication (Windows only) (#4288, #4388)
ActiveDirectoryIntegrated,ActiveDirectoryInteractive,ActiveDirectoryDeviceCodeFlow, and the deprecatedActiveDirectoryPasswordmodes.... (truncated)
7.1.0-preview1
This update brings the following changes since the 7.0.0 release:
Added
SqlBatchSupport on .NET FrameworkWhat Changed:
SqlBatchand related batch-command support for the .NET Framework target so the batching API is now available across the full supported platform matrix, includingnet462. (#3926)Who Benefits:
Impact:
SqlBatch,SqlBatchCommand, and the related execution methods are now usable on .NET Framework builds in addition to .NET.Cross-Driver Connection-String Synonym Alignment
What Changed:
ColumnEncryption,ConnectTimeout,FailoverPartner,PacketSize, andWorkstationId. (#4192)Who Benefits:
Impact:
Changed
Type Forwards for Authentication Abstractions
What Changed:
Microsoft.Data.SqlClientassembly to public authentication-related types that were moved intoMicrosoft.Data.SqlClient.Extensions.Abstractions, includingSqlAuthenticationMethod,SqlAuthenticationParameters,SqlAuthenticationProvider,SqlAuthenticationProviderException, andSqlAuthenticationToken. (#4067, #4117)Who Benefits:
Impact:
User Agent Feature Extension Enabled by Default
... (truncated)
7.0.4
This servicing release includes security updates, certificate and enclave-session validation fixes, and improvements to result reading and managed networking.
Use matching
7.0.4versions of the driver and companion packages. Assemblies retainAssemblyVersion 7.0.0.0; no new .NET Framework binding redirects are required when upgrading from7.0.3.Microsoft.SqlServer.Serveris unchanged and versioned independently.Changes Since 7.0.3
Changed
System.Security.Cryptography.Pkcs8.0.2 for net462/net8.0/netstandard2.0 and affected .NET 9 dependencies to 9.0.21.Fixed
HostNameInCertificateduring managed SNI certificate validation, even when the certificate matches the server name (net8.0/net9.0). (#4908)SqlDataReader.HasRowsreturningfalsewhen informational messages precede the first row. (#4899)GetTextReaderreads corruptingnvarchartext on big-endian platforms. (#4962)IndexOutOfRangeException. (#4978)Companion Packages
All packages below ship as
7.0.4.window_handle_requirederrors, preserving the original error code and inner exception.For Windows WAM errors, provide a parent window through
SetParentActivityOrWindowFunc, or useAuthentication=Active Directory Defaultwith a configured non-interactive credential in windowless hosts. Interactive authentication without WAM requires a customApplicationClientIdandUseWamBroker=false. WAM remains enforced for SqlClient's first-party application ID; no automatic fallback was added.Platform Support
.NET Framework 4.6.2+ on Windows and .NET 8.0+ on Windows, Linux, and macOS. Companion package targets and dependency lists are included in the linked package notes.
Thanks to LaurensVergote for contributing.
Full release notes and dependency versions
7.0.3
This update brings the following changes since the 7.0.2 release:
The core driver and its companion packages ship together as version
7.0.3. Update the companion packages you use alongside the driver to7.0.3. Assembly versions remain7.0.0.0, unchanged from7.0.2.Companion package release notes
Changed
Microsoft.Data.SqlClient.SNIandMicrosoft.Data.SqlClient.SNI.runtimedependencies to 6.0.3 (was 6.0.2).(#4599)
Fixed
Fixed a
SqlBulkCopyregression in environments where the application login cannot readsys.all_columns. Bulk copy now falls back to the earlier column-discovery behavior when that permission is unavailable. Support for hidden columns and SQL Graph column aliases still requires access to the metadata view.(#4370, #4306, #4402)
Fixed a memory-allocation regression in connection and command operations caused by formatting diagnostic strings even when tracing was disabled. Also corrected trace messages that reported an incorrect object ID or could throw
FormatExceptionwhen traced values contained braces.(#4528, #4533)
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, #4583)
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, #4553)
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, #4561)
Fixed authentication state handling so clearing
SqlConnection.AccessToken,AccessTokenCallback, orSspiContextProviderpreserves the other authentication values in the connection pool key. Cloning a connection or updating its credential also preserves itsSspiContextProvider. Combining a non-nullSspiContextProviderwithAccessTokenorAccessTokenCallbacknow throwsInvalidOperationExceptioninstead of silently discarding authentication state; applications must use one authentication mechanism at a time.(#4520, #4561, #4644)
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, #4663)
Contributors
We thank the following public contributors. Their efforts toward this project are very much appreciated.
Target Platform Support
... (truncated)
Commits viewable in compare view.
Pinned Microsoft.Data.SqlClient at 7.1.2.
Release notes
Sourced from Microsoft.Data.SqlClient's releases.
7.1.2
This servicing release includes security updates, certificate and enclave-session validation fixes, and improvements to result reading and managed networking.
Use matching
7.1.2versions of the driver and companion packages. Assemblies retainAssemblyVersion 7.0.0.0; no new .NET Framework binding redirects are required when upgrading from7.1.1.Microsoft.SqlServer.Serveris unchanged and versioned independently.Changes Since 7.1.1
Changed
System.Security.Cryptography.Pkcs8.0.2 for net462/net8.0/netstandard2.0 and affected .NET 9 dependencies, includingSystem.Threading.RateLimiting, to 9.0.21.Fixed
HostNameInCertificateduring managed SNI certificate validation, even when the certificate matches the server name (net8.0/net9.0). (#4907)SqlDataReader.HasRowsreturningfalsewhen informational messages precede the first row. (#4900)GetTextReaderreads corruptingnvarchartext on big-endian platforms. (#4961)IndexOutOfRangeException. (#4977)TypeInitializationExceptionorDllNotFoundExceptionon Unix (net8.0/net9.0). (#4770)Companion Packages
All packages below ship as
7.1.2.window_handle_requirederrors, preserving the original error code and inner exception.For Windows WAM errors, provide a parent window through
SetParentActivityOrWindowFunc, or useAuthentication=Active Directory Defaultwith a configured non-interactive credential in windowless hosts. Interactive authentication without WAM requires a customApplicationClientIdandUseWamBroker=false. WAM remains enforced for SqlClient's first-party application ID; no automatic fallback was added.Platform Support
.NET Framework 4.6.2+ on Windows and .NET 8.0+ on Windows, Linux, and macOS. Companion package targets and dependency lists are included in the linked package notes.
Thanks to LaurensVergote and shreyarao4 for contributing.
Full release notes and dependency versions
Commits viewable in compare view.
Pinned Microsoft.Extensions.DependencyInjection at 11.0.0.
Release notes
Sourced from Microsoft.Extensions.DependencyInjection's releases.
10.0.404
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.404and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.403
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.403and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.402
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.402and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.401
Release
What's Changed
... (truncated)
10.0.400
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.303
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.302
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.302and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.301
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.301and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.300
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.300and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.204
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.204and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.203
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.202
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.201
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.201and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.200
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.200and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.115
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.115and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.115-servicing.26529.108.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signature was generated from a build-produced source archive with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archive uses0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.114
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.114and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.114-servicing.26522.126.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.113
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.113and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.112
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.112and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.111
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.111and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.110
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.110and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.109
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.109and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.108
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.108and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.107
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.107and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the [dotnet/dot...
Description has been truncated