Breaking change in 1.13.0

[sebastienros]

As mentioned here this PR introduced a new parameter.
In order to not break binary compatibility the methods should have been duplicated. The old ones could still have an [Osbsolete] attribute to prefer the new ones and be dropped in a major release.

[Anush008]

Hey @sebastienros
Yes. We should have added an overload instead.
Will take more caution next time. Thanks.

[eerhardt]

@Anush008 - FYI there are tools that can prevent this kind of mistake. Check out https://learn.microsoft.com/dotnet/fundamentals/apicompat/overview for more info.

[Anush008]

Thanks.

[Anush008]

I believe this should be resolved for Aspire once Semantic Kernel updates to the latest client version.

[Anush008]

Filed microsoft/semantic-kernel#11502