Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use #opts.apiVersion #300

Merged
merged 1 commit into from
Feb 13, 2025
Merged

Use #opts.apiVersion #300

merged 1 commit into from
Feb 13, 2025

Conversation

brianbscho
Copy link

It's using 2024-10-01-preview hardcoded value without chance to change apiVersion.

In Azure document, it is stated that: "Use the latest 2024-12-17 model version".

Copy link

changeset-bot bot commented Feb 13, 2025

⚠️ No Changeset found

Latest commit: 5b3c492

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@CLAassistant
Copy link

CLAassistant commented Feb 13, 2025

CLA assistant check
All committers have signed the CLA.

@s-hamdananwar s-hamdananwar merged commit 45432d3 into livekit:next Feb 13, 2025
5 checks passed
@aaronwangj
Copy link

@theomonnom @s-hamdananwar There are a bunch of Livekit users using realtime API and we're blocked without this. Can we get this into main?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants