Skip to content

Releases: Azure-Samples/azure-search-openai-demo

2024-08-08: GPT-4o-mini support

08 Aug 18:49
55b0961
Compare
Choose a tag to compare

This release includes support for gpt-4o-mini for the chat completion requests. This support required an update to the token counting package. See instructions for switching here:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/deploy_features.md#using-gpt-4
Unfortunately, gpt-4o-mini is only in eastus, so you may need to change the location of your OpenAI resource. You can change that in .azure/ENV-NAME/config.json

What's Changed

  • Upgrade openai, openai-messages-token-helper, for gpt-4o-mini support by @dependabot in #1893

Full Changelog: 2024-08-07...2024-08-08

2024-08-07: Improved logging in prod, auth package upgrade

07 Aug 20:06
a8b1202
Compare
Choose a tag to compare

The most significant changes of this release are:

  • Improved logging in production: you should now be able to see INFO and DEBUG level logs in production, if desired, as well as the HTTP access logs.
  • Migration away from the python jose package for Entra token validation, as it was no longer maintained. Only relevant if you are using the optional authentication feature.

What's Changed

New Contributors

Full Changelog: 2024-07-22...2024-08-07

2024-07-22: Removal of VM from private network deployment

22 Jul 21:04
0a62d10
Compare
Choose a tag to compare

We previously included Bicep to enable the creation of a VM and Bastion for connection to a privately deployed app endpoint. However, due to security concerns around the VM enabling access to the endpoint, we've removed that option from deployment. To access the endpoint, you can instead use an Azure VPN gateway, Azure Virtual Desktop, other means of accessing the VNet, or add an allowance for your IP to the chat app's firewall.

What's Changed

New Contributors

Full Changelog: 2024-07-16...2024-07-22

2024-07-16: Seed parameter, Azure Verified Modules

16 Jul 23:35
b49a89c
Compare
Choose a tag to compare

This release includes:

  • the addition of a seed parameter. That is particularly helpful if you are evaluating your app.
  • a partial migration to Azure Verified Modules to reduce the amount of custom Bicep in this repo and inherit security best practices automatically. We will continue to migrate as many modules as possible.
  • an improvement to the prepdocs script so that you can pass "--removeall" and "--remove" on the CLI. You still need to modify the script to specify the filename, however.
  • a fix for the local frontend server, to address an issue with running "npm run dev" inside Dev Containers

What's Changed

Full Changelog: 2024-07-10...2024-07-16

2024-07-10: Responsive design for mobile

10 Jul 16:42
1603e94
Compare
Choose a tag to compare

This release includes improved CSS and a burger menu for smaller viewport sizes, so that the app works better for mobile phones. Please test out and report any issues.

What's Changed

New Contributors

Full Changelog: 2024-07-03...2024-07-10

2024-07-03: Authentication and security improvements

03 Jul 16:16
f4fb45c
Compare
Choose a tag to compare

The most significant change in this release is improvements to the login system to handle token refresh in the browser for users who leave the tab open for long periods of time (PR #1778). Please bring those changes in if you're using auth.
 

What's Changed

Full Changelog: 2024-06-20...2024-07-03

2024-06-20: Settings allow semantic ranker with vector search

20 Jun 21:36
b6f2493
Compare
Choose a tag to compare

The most significant change in this release is that you can try out semantic ranker with vector search, in case that's better for you than semantic ranker with hybrid search. In our tests, semantic+hybrid is always the best, but we want to make sure you can test all the combinations.

Various packages and documentation pages have also been updated.

What's Changed

New Contributors

Full Changelog: 2024-06-05...2024-06-20

2024-06-05: Conform app to new AI Chat Protocol

05 Jun 18:25
dd7c1d2
Compare
Choose a tag to compare

The big change in the latest release is that the app now confirms to the official Microsoft AI Chat Protocol, documented here:
https://github.com/microsoft/ai-chat-protocol/tree/main/spec#readme
There is also a JS SDK for that protocol that we will adopt soon to simplify our frontend parsing code.
You can see the pull request for more details, but basically:

  • Instead of sending "stream": True to get a streaming response, we send to a different path, "/chat/stream".
  • Instead of passing down the full choices list from the OpenAI response, we pass down only the first choice, specifically it's message or delta.

We have also updated the evaluator tool to work with either the new version of the backend protocol or the old, configurable via JMESPath expressions in the config JSON.

This change also includes a revamp of the Developer Settings to include tooltips, to try and make it more clear what each setting does.

What's Changed

New Contributors

Full Changelog: 2024-06-03b...2024-06-05

2024-06-03b: Speech output with browser

03 Jun 22:11
306ac38
Compare
Choose a tag to compare

You can now optionally enable speech output using the Browser SDKs, as opposed to using the Azure Speech SDK. The speech output is generally not as fluid, but it's entirely free, so it's a great zero-cost option to increase accessibility. See docs at:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/deploy_features.md#speech-output

We've also added documentation about a Python-based load balancer for OpenAI instances. See:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/productionizing.md#openai-capacity

 ## What's Changed

New Contributors

Full Changelog: 2024-06-03...2024-06-03b

2024-06-03: GPT-4O support for optional vision feature

03 Jun 16:37
a5c4cce
Compare
Choose a tag to compare

The optional vision feature now uses GPT-4O instead of GPT4-turbo-with-vision, due to much better performance.

Unfortunately, due to the difference in region availability, it may be difficult to switch to GPT-4O in your existing resource groups, depending on what region you originally picked. You may need to change the region for the OpenAI resource group in .azure/ENV-NAME/config.json, delete the previous OpenAI instance, and deploy a whole new OpenAI instance.

We did discover one vision-related splitting issue while debugging this change.

See pull request for performance statistics and more details on the change.

What's Changed

New Contributors

Full Changelog: 2024-05-29...2024-06-03