Skip to content

Releases: betalgo/openai

8.0.0

10 Apr 00:25
0ca4054
Compare
Choose a tag to compare

8.0.0

  • Added support for .NET 8.0 thanks to @BroMarduk
  • Utilities library updated to work with only .NET 8.0

What's Changed

New Contributors

Full Changelog: v7.4.7...v8.0.0

v7.4.7

06 Apr 23:22
e3a3c40
Compare
Choose a tag to compare

7.4.7

  • Fixed a bug that Vision API could not be used with Azure OpenAI, Thanks to @yt3trees
  • Fixed a bug that was blocking CreateCompletionAsStream on some platforms. #331
  • Fixed a bug that was causing an error with multiple tool calls, now we are handling index parameter #493, thanks to @David-Buyer

What's Changed

Full Changelog: v7.4.6...v7.4.7

v7.4.6

07 Feb 22:57
3475188
Compare
Choose a tag to compare

7.4.6

  • Fixed again🥲 incorrect Model Naming - moderation models and ada embedding 2 model

What's Changed

Full Changelog: v7.4.5...v7.4.6

v7.4.5

07 Feb 22:16
a56950d
Compare
Choose a tag to compare
  • Fixed function calling streaming bugs thanks to @David-Buyer @dogdie233 @gavi @Maracaipe611
  • Breaking Change:
    While streaming (CreateCompletionAsStream), there were some unexpected incoming data chunks like :pings or :events, etc. @gavi discovered this issue. We are now ignoring these chunks. If you were using it, you need to set justDataMode to false.

What's Changed

New Contributors

Full Changelog: v7.4.4...v7.4.5

7.4.4

31 Jan 00:01
67f39b3
Compare
Choose a tag to compare

7.4.4

  • Added support for new models : TextEmbeddingV3Small, TextEmbeddingV3Large, Gpt_3_5_Turbo_0125, Gpt_4_0125_preview, Gpt_4_turbo_preview, Text_moderation_007, Text_moderation_latest, Text_moderation_stable
  • Added optinal dimension and encoding for embedding thanks to @shanepowell

What's Changed

Full Changelog: v7.0.4...v7.4.4

v7.4.3

12 Dec 11:44
649f31f
Compare
Choose a tag to compare

7.4.3

  • Fixed the response format of AudioCreateSpeechRequest.
  • Updated Azure OpenAI version to 2023-12-01-preview, which now supports dall-e 3.
  • Added the ability to retrieve header values from the base response, such as ratelimit, etc. Please note that this feature is experimental and may change in the future.
  • Semi-Breaking change:
    • The SDK will now attempt to handle 500 errors and other similar errors from the OpenAI server. Previously, an exception was thrown in such cases. Now, the SDK will try to read the response and return it as an error message. This change provides more visibility to developers and helps them understand the cause of the error.

What's Changed

Full Changelog: v7.4.2...v7.4.3

7.4.2

06 Dec 21:52
3747353
Compare
Choose a tag to compare
  • Let's start with breaking changes:
    • OpenAI has replaced function calling with tools. We have made the necessary changes to our code. This is not a major change; now you just have a wrapper around your function calling, which is named as "tool". The Playground provides an example. Please take a look to see how you can update your code.
      This update was completed by @shanepowell. Many thanks to him.
  • Now we support the Vision API, which involves passing message contents to the existing chat method. It is quite easy to use, but documentation was not available in the OpenAI API documentation.
    This feature was completed by @belaszalontai. Many thanks to them.

What's Changed

New Contributors

Full Changelog: v7.4.1...v7.4.2

7.4.1

15 Nov 23:45
e382c94
Compare
Choose a tag to compare

7.4.1

What's Changed

New Contributors

  • @UsamaShahid569 made their first contribution in #417

Full Changelog: v7.4.0...v7.4.1

7.4.0

11 Nov 12:55
ec9a425
Compare
Choose a tag to compare

Version 7.4.0

What's Changed

New Contributors

Full Changelog: v7.3.1...v7.4.0

7.3.1

11 Nov 12:53
9f80263
Compare
Choose a tag to compare

Version 7.3.1

  • Reverting a breking change which will be also Breaking Changes(only for 7.3.0):
    • Reverting the usage of EnsureStatusCode() which caused the loss of error information. Initially, I thought it would help in implementing HTTP retry tools, but now I believe it is a bad idea for two reasons.
      1. You can't simply retry if the request wasn't successful because it could fail for various reasons. For example, you might have used too many tokens in your request, causing OpenAI to reject the response, or you might have tried to use a nonexistent model. It would be better to use the Error object in your retry rules. All responses are already derived from this base object.
      2. We will lose error response data.

What's Changed

Full Changelog: v7.3.0...v7.3.1