Repository navigation
Bump the nuget-dependencies group with 13 updates - #31
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 Azure.Security.KeyVault.Secrets from 4.11.1 to 4.12.0 Bumps coverlet.collector from 10.0.1 to 10.1.1 Bumps Microsoft.ApplicationInsights.AspNetCore from 3.1.2 to 3.2.0 Bumps Microsoft.AspNetCore.Authentication.OpenIdConnect from 8.0.11 to 8.0.34 Bumps Microsoft.AspNetCore.DataProtection.Abstractions from 9.0.18 to 11.0.0 Bumps Microsoft.Data.SqlClient from 7.0.2 to 7.1.2 Bumps Microsoft.Data.SqlClient.Extensions.Azure from 7.0.2 to 7.1.2 Bumps Microsoft.EntityFrameworkCore.Design from 9.0.19 to 9.0.23 Bumps Microsoft.EntityFrameworkCore.InMemory from 9.0.19 to 9.0.23 Bumps Microsoft.EntityFrameworkCore.SqlServer from 9.0.19 to 9.0.23 Bumps Microsoft.Graph from 6.6.0 to 6.10.0 Bumps Microsoft.NET.Test.Sdk from 18.9.0 to 18.12.0 Bumps xunit.runner.visualstudio from 4.0.0 to 4.0.1 --- updated-dependencies: - dependency-name: Azure.Security.KeyVault.Secrets dependency-version: 4.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Microsoft.ApplicationInsights.AspNetCore dependency-version: 3.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Microsoft.AspNetCore.Authentication.OpenIdConnect dependency-version: 8.0.34 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.AspNetCore.DataProtection.Abstractions dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-dependencies - dependency-name: Microsoft.Data.SqlClient dependency-version: 7.1.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Microsoft.Data.SqlClient.Extensions.Azure dependency-version: 7.1.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 9.0.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-version: 9.0.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.EntityFrameworkCore.SqlServer dependency-version: 9.0.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies - dependency-name: Microsoft.Graph dependency-version: 6.10.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-dependencies - dependency-name: xunit.runner.visualstudio dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF ScorecardScorecard details
Scanned Files
|
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 Azure.Security.KeyVault.Secrets from 4.11.1 to 4.12.0.
Release notes
Sourced from Azure.Security.KeyVault.Secrets's releases.
4.12.0
4.12.0 (2026-10-27)
Other Changes
2026-04-01.Commits viewable in compare view.
Updated coverlet.collector from 10.0.1 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
10.1.0
Improvements
Fixed
Diff between 10.0.1 and 10.1.0
Commits viewable in compare view.
Updated Microsoft.ApplicationInsights.AspNetCore from 3.1.2 to 3.2.0.
Release notes
Sourced from Microsoft.ApplicationInsights.AspNetCore's releases.
3.2.0
http.client.request.duration. OtherSystem.Net.Httpmetrics are now opt-in through OpenTelemetryAddView; dashboards and alerts using them must explicitly enable collection. HTTP dependency tracing and server metrics are unchanged. No new public API is introduced. Addresses the HTTP metric-volume concern in #3192.NullReferenceExceptionwhen using TelemetryClient APIs when no connection string is provided.TelemetryClient.TrackDependency(DependencyTelemetry)andTelemetryClient.TrackRequest(RequestTelemetry)now default an unsetTimestamptoDateTimeOffset.UtcNow(restoring 2.x behavior) instead of emitting0001-01-01T00:00:00Z, which ingestion rejects.enduser.pseudo.id,microsoft.session.id,microsoft.synthetic_source,microsoft.user.account_id), souser_Id,session_Id,operation_SyntheticSourceanduser_AccountIdare populated again instead of the values landing incustomDimensionsasai.user.id,session.id,ai.operation.syntheticSourceandenduser.account.user_AccountIdis also no longer skipped when the authenticated user cookie is present, and the unmappedsession.isFirstcustom dimension is no longer emitted.StartOperation/StopOperationlosing or misreporting telemetry fields. Stopping an operation now exports the fields set on its telemetry item using the same keys asTrackDependency/TrackRequest: dependencyType,Data,TargetandResultCode(previously wrong or empty for HTTP, SQL,Queue Messageand custom types), requestUrl,SourceandResponseCode,Success, and customProperties. The unmappedOperationNameandmessaging.destinationtags no longer appear as custom dimensions.Commits viewable in compare view.
Updated Microsoft.AspNetCore.Authentication.OpenIdConnect from 8.0.11 to 8.0.34.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.OpenIdConnect's releases.
8.0.34
Release
What's Changed
36ba75ftobc548fdby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from36ba75ftobc548fddotnet/aspnetcore#69625365965ftobe938cdby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/MessagePack-CSharp from365965ftobe938cddotnet/aspnetcore#69538bc548fdtob66cffcby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest frombc548fdtob66cffcdotnet/aspnetcore#69811Full Changelog: dotnet/aspnetcore@v8.0.32...v8.0.34
8.0.33
Release
Full Changelog: dotnet/aspnetcore@v8.0.32...v8.0.33
8.0.32
Release
What's Changed
3940de9to36ba75fby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from3940de9to36ba75fdotnet/aspnetcore#68922Full Changelog: dotnet/aspnetcore@v8.0.31...v8.0.32
8.0.31
Release
What's Changed
3064a60to3940de9by @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from3064a60to3940de9dotnet/aspnetcore#68173Full Changelog: dotnet/aspnetcore@v8.0.30...v8.0.31
8.0.30
Release
What's Changed
7140cd4to973323eby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from7140cd4to973323edotnet/aspnetcore#675259614e6fto365965fby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/MessagePack-CSharp from9614e6fto365965fdotnet/aspnetcore#67524973323eto3064a60by @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from973323eto3064a60dotnet/aspnetcore#67654New Contributors
Full Changelog: dotnet/aspnetcore@v8.0.29...v8.0.30
8.0.29
Release
What's Changed
d72f9c8toa721f1bby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest fromd72f9c8toa721f1bdotnet/aspnetcore#66973a721f1bto7140cd4by @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest froma721f1bto7140cd4dotnet/aspnetcore#67222Full Changelog: dotnet/aspnetcore@v8.0.28...v8.0.29
8.0.28
Release
What's Changed
Full Changelog: dotnet/aspnetcore@v8.0.27...v8.0.28
8.0.27
Release
What's Changed
73a63eatod72f9c8by @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from73a63eatod72f9c8dotnet/aspnetcore#66087Full Changelog: dotnet/aspnetcore@v8.0.26...v8.0.27
8.0.26
Release
What's Changed
56efe39to73a63eaby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from56efe39to73a63eadotnet/aspnetcore#65586Full Changelog: dotnet/aspnetcore@v8.0.25...v8.0.26
8.0.25
Release
What's Changed
9156d4cto56efe39by @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from9156d4cto56efe39dotnet/aspnetcore#65289Full Changelog: dotnet/aspnetcore@v8.0.24...v8.0.25
8.0.24
Release
8.0.23
Release
What's Changed
https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-january-2026-servicing-updates/#release-changelogs
8.0.22
Release
What's Changed
eb2d85eto9706f75by @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest fromeb2d85eto9706f75dotnet/aspnetcore#63893Full Changelog: dotnet/aspnetcore@v8.0.21...v8.0.22
8.0.21
Release
What's Changed
373af2etoeb2d85eby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from373af2etoeb2d85edotnet/aspnetcore#63500Full Changelog: dotnet/aspnetcore@v8.0.20...v8.0.21
8.0.20
Release
What's Changed
c67de11to373af2eby @dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest fromc67de11to373af2edotnet/aspnetcore#63038Full Changelog: dotnet/aspnetcore@v8.0.19...v8.0.20
8.0.18
Release
What's Changed
04ee1b4toe9092b1by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest from04ee1b4toe9092b1dotnet/aspnetcore#62201Full Changelog: dotnet/aspnetcore@v8.0.17...v8.0.18
8.0.17
Bug Fixes
The Forwarded Headers Middleware now ignores
X-Forwarded-Headerssent from unknown proxies. This change improves security by ensuring that only trusted proxies can influence the forwarded headers, preventing potential spoofing or misrouting of requests.Dependency Updates
Update dependencies from dotnet/arcade (#61832)
This update brings in the latest changes from the dotnet/arcade repository, ensuring that ASP.NET Core benefits from recent improvements, bug fixes, and security patches in the shared build infrastructure.
Bump src/submodules/googletest from
52204f7to04ee1b4(#61761)The GoogleTest submodule has been updated to a newer commit, providing the latest testing features, bug fixes, and performance improvements for the project's C++ test components.
Miscellaneous
Update branding to 8.0.17 (#61830)
The project version branding has been updated to reflect the new 8.0.17 release, ensuring consistency across build outputs and documentation.
Merging internal commits for release/8.0 (#61924)
This change merges various internal commits into the release/8.0 branch, incorporating minor fixes, documentation updates, and other non-user-facing improvements to keep the release branch up to date.
This summary is generated and may contain inaccuracies. For complete details, please review the linked pull requests.
Full Changelog: dotnet/aspnetcore@v8.0.16...v8.0.17
8.0.16
Release
What's Changed
24a9e94to52204f7by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest from24a9e94to52204f7dotnet/aspnetcore#61260Full Changelog: dotnet/aspnetcore@v8.0.15...v8.0.16
8.0.15
Release
What's Changed
e235eb3to24a9e94by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest frome235eb3to24a9e94dotnet/aspnetcore#60677Full Changelog: dotnet/aspnetcore@v8.0.14...v8.0.15
8.0.14
Release
What's Changed
7d76a23toe235eb3by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest from7d76a23toe235eb3dotnet/aspnetcore#60150Full Changelog: dotnet/aspnetcore@v8.0.13...v8.0.14
8.0.13
Release
What's Changed
d144031to7d76a23by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest fromd144031to7d76a23dotnet/aspnetcore#59678index.htmlduring development by @github-actions in [release/8.0] [Blazor WASM standalone] Avoid cachingindex.htmlduring development dotnet/aspnetcore#59349Full Changelog: dotnet/aspnetcore@v8.0.12...v8.0.13
8.0.12
Release
What's Changed
6dae7ebto1204d63by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest from6dae7ebto1204d63dotnet/aspnetcore#58741serialize-javascripttransient dependency by @MackinnonBuck in [release/8.0] Upgradeserialize-javascripttransient dependency dotnet/aspnetcore#584661204d63tod144031by @dependabot in [release/8.0] (deps): Bump src/submodules/googletest from1204d63tod144031dotnet/aspnetcore#59033Full Changelog: dotnet/aspnetcore@v8.0.11...v8.0.12
Commits viewable in compare view.
Updated Microsoft.AspNetCore.DataProtection.Abstractions from 9.0.18 to 11.0.0.
Release notes
Sourced from Microsoft.AspNetCore.DataProtection.Abstractions'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/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.106
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.106and 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.105
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.105and 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.104
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.104and 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.103
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.103and 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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
10.0.102-sb1
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.102-sb1and 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.101
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.101and 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.100
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.100and 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
To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build:
--branding rtm.10.0.100-rc.2.25502.107
You can build .NET 10.0 RC 2 from the repository by cloning the release tag
v10.0.100-rc.2.25502.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/dotnet repository.
Attached are PGP signatures for the GitHub generated tar...
Description has been truncated