Conversation
kazrael2119
requested review from
MaryGao,
deyaaeldeen,
dw511214992,
jeremymeng,
praveenkuttappan,
qiaozha and
witemple-msft
as code owners
ghost
added
the
lirenhe
left a comment
lirenhe
left a comment
There was a problem hiding this comment.
Don't quite understand the breaking, can we use the same commit of the Swagger for the exsiting SDK instead of the latest one to avoid breaking change?
Because the old commit id does not work so we take the latest one |
My understanding is by default we should use the old commit id to avoid breaking change, is it possbile to investigate why the old one does not work instead of using the latest one directly, especially the latest one contains breaking change. |
| resourceGroupName, | ||
| profileName, | ||
| endpointName, | ||
| customDomainName, |
There was a problem hiding this comment.
We need to revert these changes
|
|
||
| // #endregion | ||
|
|
||
| // Operation Specifications |
5 participants
release issue：https://github.com/Azure/sdk-release-request/issues/3545