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

[AI Language API] Is the sdk going to be affected by retirement of Language API 2024-05-15-preview and backwards? #39504

Open
hamer101 opened this issue Jan 31, 2025 · 3 comments
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@hamer101
Copy link

As addressed in the title.
We've been informed that "Azure AI Language preview APIs (2024-05-15-preview or earlier versions) will be retired on 31 March 2025" and thus we should "Transition to the latest preview or GA version of Azure AI Language API".

My concern rises from the fact that there's no communication about the way it propagates to SDK modules, as, for example, the textanalytics module is still operating on an API version from 2023.
I suspect that it won't be affected, since the API in use is Generally Available, which, as the notification indirectly suggests, should be out of scope for that change.

Either way, I'd want verify my suspicion, or get to know whether any related changes will occur to that SDK in the span of nearest months.

Thanks in advance.

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 31, 2025
@xiangyan99 xiangyan99 removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 31, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 31, 2025
@xiangyan99
Copy link
Member

Thanks for reaching out.

Could you share the information that which library do you use?

@xiangyan99 xiangyan99 added the needs-author-feedback Workflow: More information is needed from author to address the issue. label Jan 31, 2025
@github-actions github-actions bot removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 31, 2025
Copy link

Hi @hamer101. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

@kristapratico kristapratico added the Client This issue points to a problem in the data-plane of the library. label Feb 4, 2025
@hamer101
Copy link
Author

hamer101 commented Feb 4, 2025

I'm using libraries that utilise the mentioned API, ex. the current textanalytics, but that's beside the point - I'm asking whether any part of the sdk is going to be updated due to that API retirement.

@github-actions github-actions bot added needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-author-feedback Workflow: More information is needed from author to address the issue. labels Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants