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

[core] - Move core-rest-pipeline and packages that depend on it to core-tracing Preview 12 #15874

Closed
maorleger opened this issue Jun 21, 2021 · 1 comment
Assignees
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Milestone

Comments

@maorleger
Copy link
Member

maorleger commented Jun 21, 2021

Because core-rest-pipeline 1.1.0 is in beta, and packages still depend on 1.0.x core-rest-pipeline, we're unable to upgrade them to core-tracing preview 12 without a hotfix to core-rest-pipeline.

We already upgraded all the core-http based packages to core-tracing preview 12. This issue tracks upgrading the rest of them. It's blocked; however, pending GA of core-rest-pipeline 1.1.0

If we move core-tracing to 1.0.0 this issue will track moving the rest of the packages to that version.

@maorleger maorleger added Client This issue points to a problem in the data-plane of the library. Azure.Core labels Jun 21, 2021
@maorleger maorleger added this to the [2021] August milestone Jun 21, 2021
@maorleger maorleger self-assigned this Jun 21, 2021
@maorleger maorleger modified the milestones: [2021] August, [2021] July Jun 25, 2021
@maorleger
Copy link
Member Author

Closed via #15923

openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-js that referenced this issue Sep 15, 2021
Adding 202 Accepted for deletion call (Azure#15874)

* Adding 202 for deletion call

* Adding headers to suppress warnings
@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
Azure.Core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

1 participant