[release/9.1] Update Microsoft.Extensions.AI to 9.3.0-preview.1.25114.11 (#7643) #7657
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.
Backport of #7643 to release/9.1
/cc @stephentoub
Customer Impact
When we ship 9.1, users won't be getting the latest versions of our dependencies. Specifically, they won't be getting the latest version of Microsoft.Extensions.AI. And MEAI has had breaking API changes (because they are still in preview) which may cause problems if users try using the new version with Aspire.
This needed to update to all .NET package versions because a new MEAI brings in new versions transitively. CPM doesn't like it when you have mismatched versions. So I brought them all up to date with the release last week.
Testing
Existing tests
Risk
Relatively low. Just updating to the newest versions. Tests are all passing.
Regression?
No.