Bump Microsoft.AspNetCore.Authentication.JwtBearer and 10 others#6
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump Microsoft.AspNetCore.Authentication.JwtBearer and 10 others#6dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.2 to 10.0.8 Bumps Microsoft.AspNetCore.Components.WebAssembly from 10.0.2 to 10.0.8 Bumps Microsoft.AspNetCore.Components.WebAssembly.DevServer from 10.0.2 to 10.0.8 Bumps Microsoft.AspNetCore.OpenApi from 10.0.2 to 10.0.8 Bumps Microsoft.Extensions.Caching.Hybrid from 10.5.0 to 10.6.0 Bumps Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.2 to 10.0.8 Bumps Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore from 10.0.2 to 10.0.8 Bumps Microsoft.Extensions.Hosting.Abstractions from 10.0.7 to 10.0.8 Bumps Microsoft.Extensions.Http.Resilience from 10.1.0 to 10.6.0 Bumps Microsoft.Extensions.Logging.Abstractions to 10.0.8 Bumps Microsoft.Extensions.ServiceDiscovery from 10.1.0 to 10.6.0 --- updated-dependencies: - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.AspNetCore.Components.WebAssembly dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.AspNetCore.Components.WebAssembly.DevServer dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.Caching.Hybrid dependency-version: 10.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.Caching.StackExchangeRedis dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.Hosting.Abstractions dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.Logging.Abstractions dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: microsoft-extensions - dependency-name: Microsoft.Extensions.ServiceDiscovery dependency-version: 10.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: microsoft-extensions ... Signed-off-by: dependabot[bot] <support@github.com>
ff53584 to
dacb3d6
Compare
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
This was referenced May 23, 2026
emeraldleaf
added a commit
that referenced
this pull request
May 24, 2026
#25) * fix(service-defaults): security trio — middleware order, JWT, error trace ID Three small but distinct security hardening fixes in ServiceDefaults (addresses architecture-review findings #3, #5, #6). 1. MIDDLEWARE ORDER — CorrelationIdMiddleware after UseAuthentication The middleware reads ClaimTypes.NameIdentifier from context.User to populate the UserId logger scope key. Pre-auth, context.User is empty, so UserId was silently always null for every authenticated request — defeating half the context-propagation pipeline. UserId never made it into log scopes from the HTTP entry point and never reached Wolverine envelope headers via the ActivityBaggage → OutgoingContextMiddleware path. Reordered: UseExceptionHandler → UseAuthentication → UseAuthorization → CorrelationIdMiddleware. ExceptionHandler stays first so it still wraps everything below it. 2. JWT — explicit ValidateIssuerSigningKey + tightened ClockSkew ValidateIssuerSigningKey was implicit (JWT Bearer's default validates against JWKS-discovered keys). Made explicit so it's auditable + prevents a future config change from silently disabling it. ClockSkew defaulted to 5 MINUTES. Revoked/expired tokens were accepted for 5 extra minutes — material on typical 15-minute access-token lifetimes. Set to 30 seconds: covers reasonable inter-server clock drift, doesn't give attackers a long replay window. 3. EXCEPTION HANDLER — TraceId only, not full Activity.Id Activity.Current?.Id returns the full W3C traceparent ("00-<trace>-<span>-<flags>") and we were embedding that in every ProblemDetails response. The span ID is information about server-side handler call structure that clients have no business seeing. Switched to Activity.Current?.TraceId.ToString() — same correlation utility, no leak of internal call graph. None of the three needed any consumer changes; all are internal to ServiceDefaults. Build clean (the one CS0436 warning is the pre-existing benchmarks Program-conflict; unaffected). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(service-defaults): place CorrelationIdMiddleware between Auth and Authz CodeRabbit (PR #25) flagged that the previous fix moved the middleware too far down — to AFTER UseAuthorization — which works for populating UserId but drops the audit trail for 401/403 unauthorized-attempt logs. Correct placement is BETWEEN UseAuthentication and UseAuthorization: app.UseExceptionHandler(); app.UseAuthentication(); // populates context.User app.UseMiddleware<CorrelationIdMiddleware>(); // reads User, opens scope app.UseAuthorization(); // any 401/403 here has UserId in scope Two reasons: 1. CorrelationIdMiddleware needs context.User populated to read NameIdentifier (the original ordering bug — pre-auth, User was empty and UserId was always null). 2. Placing it BEFORE Authorization means the UserId scope is active during the authorization decision. If a user is rejected, the log line says "user X tried Y and was denied" — the audit trail we need. My previous fix dropped this by placing the middleware after Authorization, which would only attribute requests that actually passed authorization. Build clean. Single-line move of one app.UseMiddleware call. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * test(service-defaults): unit tests for JWT options + GlobalExceptionHandler Covers the production-code changes in this PR so Codecov's patch-coverage gate stops complaining (was 8.33%; the prior fixes were uncovered because ServiceDefaults had no dedicated tests). GlobalExceptionHandlerTests (3): - TryHandleAsync_WhenActivityIsActive_ReturnsTraceIdOnly_NotFullActivityId: pins the security-critical change (Activity.Id → TraceId.ToString()). Asserts the response traceId equals activity.TraceId.ToString(), NOT activity.Id (which is the full W3C traceparent including span ID). Also asserts no hyphens — distinguishes the bare trace from the full "00-trace-span-flags" format. - TryHandleAsync_WhenNoActivity_FallsBackToHttpContextTraceIdentifier: covers the null-coalesce path. - TryHandleAsync_AlwaysReturnsProblemDetailsWithGenericDetail_NeverExceptionMessage: defense against information disclosure (CLAUDE.md "Error Handling"). Asserts the raw exception message doesn't appear in the response body even when the message contains sensitive-looking content like SQL. ServiceDefaultsJwtTests (3): - AddServiceDefaults_WhenAuthorityConfigured_SetsExplicitSigningKeyValidation - AddServiceDefaults_WhenAuthorityConfigured_SetsTightClockSkew - AddServiceDefaults_WhenAuthorityConfigured_RetainsCoreValidations All three boot a real Host.CreateApplicationBuilder + AddServiceDefaults with a configured authority, resolve the IOptionsMonitor<JwtBearerOptions>, and assert the TokenValidationParameters. Pins both the new hardening (ClockSkew=30s, ValidateIssuerSigningKey=true) AND the pre-existing core validations (Audience/Issuer/Lifetime) so a future refactor can't drop either silently. All 6 tests pass in 0.7s. Build clean (the one CS0436 warning is the pre-existing benchmarks Program-conflict; unaffected). Test placement follows the existing convention — ServiceDefaults tests live in service-test projects (OrderService.Tests.Unit/Application/ already has ContextPropagationMiddlewareTests, CorrelationIdMiddlewareTests, OutgoingContextMiddlewareTests). Not ideal long-term (duplication risk across the 4 service test projects), but matches the established pattern. The middleware-ordering change in Extensions.cs is harder to unit-test — it requires booting WebApplicationFactory and asserting the order of middleware execution at request time. Filed as a project-board issue for later; the JWT and ExceptionHandler tests cover the highest-risk lines of this PR (security hardening that could silently regress). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
emeraldleaf
added a commit
that referenced
this pull request
May 25, 2026
…SA services) Adds an entry to "Recently landed" capturing: - Motivation (Anton Martyniuk's "6 .NET Trends" #5 + #6, simplicity-team reviewer optics) - What changed across each service (rules → OrderService → ShippingService → PaymentService → NotificationService → CatalogService carve-out) - The PaymentRecoveryJob outbox-atomic wrap that got inlined - The CatalogService Clean-Architecture carve-out and why it's load-bearing - Test coverage: 23 mocked-repo handler tests deleted (existing integration suite covers most; remaining gap acknowledged for Shipping + Payment integration projects) - Walkthrough updates Updates "Last updated" timestamp to reflect this change. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Pinned Microsoft.AspNetCore.Authentication.JwtBearer at 10.0.8.
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.Components.WebAssembly from 10.0.2 to 10.0.8.
Release notes
Sourced from Microsoft.AspNetCore.Components.WebAssembly's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Components.WebAssembly.DevServer from 10.0.2 to 10.0.8.
Release notes
Sourced from Microsoft.AspNetCore.Components.WebAssembly.DevServer's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.OpenApi from 10.0.2 to 10.0.8.
Release notes
Sourced from Microsoft.AspNetCore.OpenApi's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned Microsoft.Extensions.Caching.Hybrid at 10.6.0.
Release notes
Sourced from Microsoft.Extensions.Caching.Hybrid's releases.
10.6.0
Version 10.6.0 stabilizes the response continuation token and background-response APIs in Microsoft.Extensions.AI.Abstractions. Most other AI work for May shipped in 10.5.1; this monthly release rolls those changes up alongside dependency updates and a small Resource Monitoring cleanup.
Experimental API Changes
Now Stable
MEAI001) #7512What's Changed
AI
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.5.2...v10.6.0
10.5.2
This patch release ships a single fix to
Microsoft.Extensions.VectorData.Abstractions, correctingStorageNameresolution when external serialization is enabled.Microsoft.Extensions.VectorData.ConformanceTests,Microsoft.Extensions.AI.Abstractions,Microsoft.Extensions.AI, andMicrosoft.Extensions.AI.OpenAIare published alongside it for version coherency — they contain no code changes from 10.5.1.Packages in this release
What's Changed
Microsoft.Extensions.VectorData.Abstractions
StorageNamebehavior when external serialization is enabled, and disable a warning fornet462. (by @roji in #7475)Full Changelog: dotnet/extensions@v10.5.1...v10.5.2
10.5.1
Version 10.5.1 of the Microsoft.Extensions.AI packages stabilizes CodeInterpreter, WebSearch, and ImageGeneration tool content types. The release adds new experimental tool search and OpenAI request policy hooks. And the OpenTelemetry gen-ai semantic conventions are updated to align with v1.41.
The 'aiagent-webapi' project template in Microsoft.Agents.AI.ProjectTemplates is updated to align with v1.3.0 of Agent Framework, updating the OpenTelemetry dependencies within the template projects as well.
Packages in this release
Experimental API Changes
Now Stable
The following types previously emitted the
MEAI001experimental diagnostic and are now stable.CodeInterpreterToolCallContentCodeInterpreterToolResultContentWebSearchToolCallContentWebSearchToolResultContentImageGenerationToolCallContentImageGenerationToolResultContentHostedImageGenerationToolImageGenerationOptionsImageGenerationResponseFormat(theHostedenum value remains experimental)IImageGeneratorand the rest of the image generation infrastructure also remain experimentalNew Experimental APIs
The following new APIs emit the
MEAI001experimental diagnostic.HostedToolSearchToolwithDeferredToolsfor tool-search-driven deferred tool loading #7471OpenAIRequestPoliciesextension hook for appendingSystem.ClientModel.PipelinePolicyinstances to outgoing OpenAI requests #7495Breaking Changes to Experimental APIs
WebSearchToolResultContent.Resultswas renamed toOutputsas part of the stabilization in #7493, aligning withCodeInterpreterToolResultContent.Outputs. The originalResultsproperty was included in version 10.4.0 and 10.5.0; this is a binary breaking change and consumers need to update to consume the updated property.... (truncated)
Commits viewable in compare view.
Pinned Microsoft.Extensions.Caching.StackExchangeRedis at 10.0.8.
Release notes
Sourced from Microsoft.Extensions.Caching.StackExchangeRedis's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore at 10.0.8.
Release notes
Sourced from Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned Microsoft.Extensions.Hosting.Abstractions at 10.0.8.
Release notes
Sourced from Microsoft.Extensions.Hosting.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Pinned Microsoft.Extensions.Http.Resilience at 10.6.0.
Release notes
Sourced from Microsoft.Extensions.Http.Resilience's releases.
10.6.0
Version 10.6.0 stabilizes the response continuation token and background-response APIs in Microsoft.Extensions.AI.Abstractions. Most other AI work for May shipped in 10.5.1; this monthly release rolls those changes up alongside dependency updates and a small Resource Monitoring cleanup.
Experimental API Changes
Now Stable
MEAI001) #7512What's Changed
AI
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.5.2...v10.6.0
10.5.2
This patch release ships a single fix to
Microsoft.Extensions.VectorData.Abstractions, correctingStorageNameresolution when external serialization is enabled.Microsoft.Extensions.VectorData.ConformanceTests,Microsoft.Extensions.AI.Abstractions,Microsoft.Extensions.AI, andMicrosoft.Extensions.AI.OpenAIare published alongside it for version coherency — they contain no code changes from 10.5.1.Packages in this release
What's Changed
Microsoft.Extensions.VectorData.Abstractions
StorageNamebehavior when external serialization is enabled, and disable a warning fornet462. (by @roji in #7475)Full Changelog: dotnet/extensions@v10.5.1...v10.5.2
10.5.1
Version 10.5.1 of the Microsoft.Extensions.AI packages stabilizes CodeInterpreter, WebSearch, and ImageGeneration tool content types. The release adds new experimental tool search and OpenAI request policy hooks. And the OpenTelemetry gen-ai semantic conventions are updated to align with v1.41.
The 'aiagent-webapi' project template in Microsoft.Agents.AI.ProjectTemplates is updated to align with v1.3.0 of Agent Framework, updating the OpenTelemetry dependencies within the template projects as well.
Packages in this release
Experimental API Changes
Now Stable
The following types previously emitted the
MEAI001experimental diagnostic and are now stable.CodeInterpreterToolCallContentCodeInterpreterToolResultContentWebSearchToolCallContentWebSearchToolResultContentImageGenerationToolCallContentImageGenerationToolResultContentHostedImageGenerationToolImageGenerationOptionsImageGenerationResponseFormat(theHostedenum value remains experimental)IImageGeneratorand the rest of the image generation infrastructure also remain experimentalNew Experimental APIs
The following new APIs emit the
MEAI001experimental diagnostic.HostedToolSearchToolwithDeferredToolsfor tool-search-driven deferred tool loading #7471OpenAIRequestPoliciesextension hook for appendingSystem.ClientModel.PipelinePolicyinstances to outgoing OpenAI requests #7495Breaking Changes to Experimental APIs
WebSearchToolResultContent.Resultswas renamed toOutputsas part of the stabilization in #7493, aligning withCodeInterpreterToolResultContent.Outputs. The originalResultsproperty was included in version 10.4.0 and 10.5.0; this is a binary breaking change and consumers need to update to consume the updated property.... (truncated)
10.5.0
HTTP Logging Middleware APIs in
Microsoft.AspNetCore.Diagnostics.Middlewareare now stable. This release also transfersMicrosoft.Extensions.VectorData.AbstractionsandMicrosoft.Extensions.VectorData.ConformanceTestsfrom the Semantic Kernel repository into dotnet/extensions, jumping from 10.1.0 to 10.5.0 for consistent versioning. The release also delivers fixes across the AI libraries, AI Evaluation, and Service Discovery.Breaking Changes
VectorStoreVectorAttributeconstructor parameter #7460Dimensionsparameter was renamed todimensions(lowercase). This is a source-breaking change only — binary compatibility is preserved.new VectorStoreVectorAttribute(Dimensions: 1536), update it tonew VectorStoreVectorAttribute(dimensions: 1536).Experimental API Changes
Now Stable
EXTEXP0013):AddHttpLogEnricher<T>,IHttpLogEnricher, andRequestHeadersLogEnricherOptions.HeadersDataClasses#7380What's Changed
AI
Vector Data
AI Evaluation
ASP.NET Core Extensions
Service Discovery
Documentation Updates
Test Improvements
... (truncated)
10.4.1
This release of the Microsoft.Extensions.AI packages adds new experimental APIs for Realtime client sessions and Text-to-Speech, along with OpenTelemetry and middleware improvements.
Packages in this release
Experimental API Changes
New Experimental APIs
Changes to Experimental APIs
NotSupportedException#7394What's Changed
AI
ITextToSpeechClientabstraction, middleware, and OpenAI implementation #7381 by @stephentoubVoiceActivityDetectionoptions to realtime session abstractions #7399 by @tarekghUriContentmediaTypeparameter optional with inference from URI file extension #7398 by @stephentoub (co-authored by @Copilot)gen_ai.client.operation.exceptionviaILogger LoggerMessageon OpenTelemetry instrumentation classes #7379 by @stephentoub (co-authored by @Copilot)invoke_workflowas an equivalent parent span toinvoke_agentinFunctionInvokingChatClient#7382 by @stephentoub (co-authored by @Copilot)HostedFileDownloadStreamexplicitly read-only #7394 by @stephentoub (co-authored by @Copilot)Documentation Updates
Test Improvements
Repository Infrastructure Updates
Acknowledgements
... (truncated)
10.4.0
This release advances the AI abstractions with new hosted file, web search, and reasoning content types, stabilizes MCP and tool approval APIs, adds streaming latency metrics to OpenTelemetry instrumentation, and delivers bug fixes across caching, data ingestion, and resource monitoring.
Experimental API Changes
Now Stable
MEAI001) #7299FakeLogCollector.GetLogsAsync(CancellationToken)is now stable (previouslyEXTEXP0003) #7332New Experimental APIs
AddExtendedHttpClientLoggingoverloads withwrapHandlersPipelineparameter (EXTEXP0013) #7231Removed Experimental APIs
MEAI001) #7353What's Changed
AI
Telemetry and Observability
HTTP Resilience and Diagnostics
... (truncated)
10.3.0
Experimental API Changes
Now Stable
IChatReducerinterface — graduated from experimental to stable. The interface is now stable; concrete implementations (MessageCountingChatReducer,SummarizingChatReducer,ReducingChatClient) remain experimental. #7235 by @jeffhandleyFunctionCallContentandFunctionResultContentunsealed — changed fromsealed classtoclass, enabling derivation. #7229 by @stephentoub (co-authored by @Copilot)Breaking Changes to Experimental APIs
MEAI001diagnostic ID was split into feature-specific constants. OpenAI-specific experimental APIs now useOPENAI001,OPENAI002, orSCME0001instead ofMEAI001. Consumers who suppressedMEAI001for OpenAI APIs may need to suppressOPENAI001/OPENAI002instead. #7116 by @jeffhandley (co-authored by @Copilot), #7235 by @jeffhandleyNew Experimental APIs
MessageCountingChatReducer,SummarizingChatReducer,ReducingChatClient, andUseChatReducerbuilder extension. #7235 by @jeffhandleyOPENAI001,OPENAI002). #7235 by @jeffhandleyImageGenerationToolCallContentandImageGenerationToolResultContent— added to JSON serialization infrastructure. #7275 by @stephentoub (co-authored by @Copilot)What's Changed
AI
Diagnostics, Health Checks, and Resource Monitoring
Service Discovery
... (truncated)
10.2.0
What's Changed
SummarizingChatReducerintegration tests by @MackinnonBuck in Fix expected conversation length inSummarizingChatReducerintegration tests dotnet/extensions#7119New Contributors
Full Changelog: dotnet/extensions@v10.1...v10.2.0
Commits viewable in compare view.
Pinned Microsoft.Extensions.Logging.Abstractions at 10.0.8.
Release notes
Sourced from Microsoft.Extensions.Logging.Abstractions's releases.
10.0.0-preview.6.25358.103
You can build .NET 10.0 Preview 6 from the repository by cloning the release tag
v10.0.0-preview.6.25358.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 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.0-preview.5.25277.114
You can build .NET 10.0 Preview 5 from the repository by cloning the release tag
v10.0.0-preview.5.25277.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
10.0.0-preview.4.25258.110
You can build .NET 10.0 Preview 4 from the repository by cloning the release tag
v10.0.0-preview.4.25258.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.0-preview.3.25171.5
You can build .NET 10.0 Preview 3 from the repository by cloning the release tag
v10.0.0-preview.3.25171.5and 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.0-preview.2.25163.2
You can build .NET 10.0 Preview 2 from the repository by cloning the release tag
v10.0.0-preview.2.25163.2and 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.0-preview.1.25080.5
You can build .NET 10.0 Preview 1 from the repository by cloning the release tag
v10.0.0-preview.1.25080.5and 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
9.0.117
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.117and 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
9.0.116
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.116and 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
9.0.115
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.114
You can build .NET 9.0 from the repository by cloning the release tag
v9.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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
9.0.113
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.112
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.111
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.110
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.109
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.101
You can build .NET 9.0 from the repository by cloning the release tag
v9.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
9.0.7
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.7and 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
9.0.6
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.6and 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
9.0.5
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.5and 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
9.0.4
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.4and 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
9.0.3
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.3and 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
9.0.2
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.2and 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
9.0.1
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.1and 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
9.0.0
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.0and 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
9.0.0-rc.2.24473.5
You can build NET 9.0 RC2 from the repository by cloning the release tag
v9.0.0-rc.2.24473.5and 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
9.0.0-rc.1.24431.7
You can build .NET 9.0 RC1 from the repository by cloning the release tag
v9.0.0-rc.1.24431.7and 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
9.0.0-preview.7.24405.7
You can build .NET 9.0 Preview 7 from the repository by cloning the release tag
v9.0.0-preview.7.24405.7and 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
9.0.0-preview.6.24327.7
You can build .NET 9.0 Preview 6 from the repository by cloning the release tag
v9.0.0-preview.6.24327.7and 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
9.0.0-preview.5.24306.7
You can build .NET 9.0 Preview 5 from the repository by cloning the release tag
v9.0.0-preview.5.24306.7and 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
9.0.0-preview.4.24266.19
You can build .NET 9.0 Preview 4 from the repository by cloning the release tag
v9.0.0-preview.4.24266.19and 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
9.0.0-preview.3.24172.9
You can build .NET 9.0 Preview 3 from the repository by cloning the release tag
v9.0.0-preview.3.24172.9and 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
9.0.0-preview.2.24128.5
You can build .NET 9.0 Preview 2 from the repository by cloning the release tag
v9.0.0-preview.2.24128.5and 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
9.0.0-preview.1.24080.9
You can build .NET 9.0 Preview 1 from the repository by cloning the release tag
v9.0.0-preview.1.24080.9and 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
8.0.127
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.127and 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
8.0.126
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.126and 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
8.0.125
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.125and 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
8.0.124
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.124and 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
8.0.123
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.123and 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
8.0.122
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.122and 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
8.0.121
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.121and 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
8.0.120
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.120and 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
8.0.119
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.119and 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
8.0.100-preview.1
8.0.18
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.18and 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
8.0.17
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.17and 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
8.0.16
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.16and 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
8.0.15
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.15and 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
8.0.14
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.14and 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
8.0.13
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.13and 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
8.0.12
You can build .NET 8.0 from the repository by cloning the release tag
v8.0.12and 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 repos...
Description has been truncated