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

Update the new @azure/communication-network-traversal package to use the latest code generator #18689

Closed
ramya-rao-a opened this issue Nov 15, 2021 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Communication

Comments

@ramya-rao-a
Copy link
Contributor

The @azure/communication-network-traversal package is currently using 6.0.0-dev.20200623.2 version of the autorest.typescript extension to the code generator. See https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/communication/communication-network-traversal/swagger/README.md

This version is more than a year old. We should instead be using the latest version which is 6.0.0-beta.15

Please note that this will update your dependencies from @azure/core-http to @azure/core-rest-pipeline which is expected. You can see the details about this move in https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/core/core-rest-pipeline/documentation/core2.md

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 15, 2021
@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Communication labels Nov 15, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 15, 2021
@ramya-rao-a ramya-rao-a added this to the [2022] January milestone Nov 15, 2021
@petrsvihlik
Copy link
Contributor

done in #21193

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Communication
Projects
None yet
Development

No branches or pull requests

3 participants