Update Azure.AI.OpenAI

[Eric StJohn (ericstj)]

Stephen Toub (@stephentoub) Jeff Handley (@jeffhandley)

I think we need this for MEAI.

Using the latest OpenAI package breaks Azure.AI.OpenAI. The latest MEAI packages soon to be released reference this latest version of OpenAI so this breaks "file->new-project" for those when they rely on the Aspire reference to bring in Azure.AI.OpenAI. There's a workaround, but ideally this can get fixed.

[Copilot]

Pull Request Overview

This PR updates the Azure.AI.OpenAI package version from 2.2.0-beta.5 to 2.3.0-beta.1, which is needed for Microsoft Extensions AI (MEAI) support.

Key Changes

• Upgrades Azure.AI.OpenAI dependency to a newer beta version

[Eric StJohn (ericstj)]

I went ahead and updated MEAI as well. Jose Perez Rodriguez (@joperezr) Eric Erhardt (@eerhardt) did you want to take a look?

[Jose Perez Rodriguez (joperezr)]

Thanks Eric StJohn (@ericstj)

[Jose Perez Rodriguez (joperezr)]

We haven't updated to latest dotnet servicing, which is likely what is causing your build failures. I can push a change tomorrow that will take care of that.

[Eric Erhardt (eerhardt)]

Using the latest OpenAI package breaks Azure.AI.OpenAI.

Eric StJohn (@ericstj) Stephen Toub (@stephentoub) - The version of OpenAI changed from 2.2.0 to 2.3.0. If there is a binary breaking change (that breaks a pretty major consumer), shouldn't OpenAI have incremented the major version?

[Eric StJohn (ericstj)]

It seems that right now there is this tight internal coupling between OpenAI and Azure.OpenAI and they are working on fixing it. Some of this discussed here openai/openai-dotnet#589