chore(deps): update dotnet monorepo to v10 - #41
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 12, 2024 10:36
f2ff7ee to
a342a91
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
November 12, 2024 19:30
a342a91 to
e2b876e
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
January 14, 2025 23:58
e2b876e to
cafd692
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
February 11, 2025 22:48
cafd692 to
04bb1d3
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
March 11, 2025 21:56
04bb1d3 to
d3c234c
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
April 8, 2025 22:11
e2f7506 to
4c6b3ba
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
May 13, 2025 22:43
4c6b3ba to
ec828c2
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
June 10, 2025 22:38
ec828c2 to
e8a8612
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
July 8, 2025 19:51
e8a8612 to
8e99d79
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
August 5, 2025 05:01
e8860ec to
a3040c7
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
August 12, 2025 20:55
a3040c7 to
c2a184b
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 9, 2025 17:39
c2a184b to
8202e68
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 9, 2025 21:40
8202e68 to
4152cc7
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
September 25, 2025 02:33
3c2b9e9 to
e48c56c
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
October 15, 2025 12:06
e48c56c to
6a707bf
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
November 16, 2025 15:51
6a707bf to
c1eff19
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
December 13, 2025 04:13
c1eff19 to
9a2c190
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
January 14, 2026 20:08
9a2c190 to
a8cf38d
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
February 11, 2026 12:14
a8cf38d to
860b7ab
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
March 14, 2026 18:20
860b7ab to
57ca39a
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
April 19, 2026 04:41
57ca39a to
8b83c9d
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
April 30, 2026 02:31
8b83c9d to
9b584e5
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
May 13, 2026 07:38
9b584e5 to
fb989e9
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
4 times, most recently
from
May 27, 2026 20:54
ee1ad5b to
a05fe64
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
June 14, 2026 19:04
a05fe64 to
79215a3
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
July 25, 2026 08:06
79215a3 to
abcc03a
Compare
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.
This PR contains the following updates:
8.0.8→10.0.108.0.8→10.0.108.0.7→10.0.108.0.8→10.0.108.0.8→10.0.108.9.1→10.8.08.2.0→10.8.08.0→10.08.0→10.0Release Notes
dotnet/dotnet (Microsoft.AspNetCore.Authentication.JwtBearer)
v10.0.10v10.0.9v10.0.8v10.0.7v10.0.6v10.0.5v10.0.4v10.0.3v10.0.2v10.0.1v9.0.7: .NET 9.0.7You 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
v9.0.6: .NET 9.0.6You 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
v9.0.5: .NET 9.0.5You 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
v9.0.4: .NET 9.0.4You 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
v9.0.3: .NET 9.0.3You 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
v9.0.2: .NET 9.0.2You 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
v9.0.1: .NET 9.0.1You 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
v9.0.0: .NET 9.0.0You 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
v8.0.18: .NET 8.0.18You 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
v8.0.17: .NET 8.0.17You 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
v8.0.16: .NET 8.0.16You 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
v8.0.15: .NET 8.0.15You 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
v8.0.14: .NET 8.0.14You 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
v8.0.13: .NET 8.0.13You 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
v8.0.12: .NET 8.0.12You 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 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
v8.0.11: .NET 8.0.11You can build .NET 8.0 from the repository by cloning the release tag
v8.0.11and 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
v8.0.10: .NET 8.0.10You can build .NET 8.0 from the repository by cloning the release tag
v8.0.10and 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
dotnet/extensions (Microsoft.Extensions.Http.Resilience)
v10.8.0This release adds new experimental APIs to Microsoft.Extensions.AI.Abstractions and updates the OpenAI dependency to 2.12.0, alongside documentation, test, and repository maintenance.
Experimental API Changes
New Experimental APIs
AIFunctionNameAttributeandAIParameterNameAttribute#7610 by @jozkee (co-authored by @jeffhandley @Copilot)ToolApprovalRequestContent.RequiresConfirmation(MEAI001) #7549 by @javiercn (co-authored by @Copilot)What's Changed
AI
Vector Data
Documentation Updates
Test Improvements
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.7.0...v10.8.0
v10.7.0v10.7.0 graduates the Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetes package to stable. The package registers a Kubernetes-aware
ResourceQuotaProviderthat reads the pod's CPU and memory requests and limits and exposes them toMicrosoft.Extensions.Diagnostics.ResourceMonitoringas baseline and maximum quotas, which then feed the request and limit dimensions of the published resource utilization metrics. The companionResourceQuotaandResourceQuotaProvidertypes inMicrosoft.Extensions.Diagnostics.ResourceMonitoringgraduate to stable in the same change so that consumers can implement custom quota providers without taking an experimental dependency.On the AI side,
Microsoft.Extensions.AI.OpenAImoves to OpenAI 2.11.0 and fixes a deserialization bug inToolJson.AdditionalPropertiesso that JSON SchemaadditionalPropertiesvalues shaped as sub-schema objects (for example{"type":"string"}) are preserved instead of throwing during deserialization.HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtgraduate to stable since both values are consistently available across hosted-file providers, whilePurposeandScoperemain experimental as provider-shaped vocabulary.FunctionInvokingChatClientdrops a backward-compat path that auto-markedToolApprovalResponseContententries withInformationalOnly: true; consumers that need to continue accepting sessions serialized before #7468 can use the sampleApprovalHistoryNormalizingChatClientmiddleware added in the test project.Experimental API Changes
Now Stable
Microsoft.Extensions.Diagnostics.ResourceMonitoring.Kubernetespackage is now stable #7253ResourceQuotaandResourceQuotaProviderAPIs are now stable (previouslyEXTEXP0008) #7253HostedFileContent.SizeInBytesandHostedFileContent.CreatedAtare now stable (previouslyMEAI001) #7513What's Changed
AI
Diagnostics, Health Checks, and Resource Monitoring
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.6.0...v10.7.0
v10.6.0Version 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
v10.5.0HTTP 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
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.4.1...v10.5.0
v10.4.0This 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
Diagnostics, Health Checks, and Resource Monitoring
Data Ingestion
Caching
Test Improvements
Repository Infrastructure Updates
Acknowledgements
Full Changelog: dotnet/extensions@v10.3.0...v10.4.0
v10.3.0What's Changed
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.