Tom Harvey

@navba-MSFT @raych1 @JackTn here's the latest example of where this is causing issues: https://github.com/Azure/azure-rest-api-specs/pull/25142#event-10398092696 - is there a timeline for this to be fixed?

@navba-MSFT @raych1 @JackTn yet another example: https://github.com/Azure/azure-rest-api-specs/pull/25435#issuecomment-1742480172

Yet another couple of examples: https://github.com/Azure/azure-rest-api-specs/pull/27524 https://github.com/Azure/azure-rest-api-specs/pull/25435

Waiting on the Service Team..

There's no breaking changes in this PR, it's renaming a segment to be consistent, which is unfortunately flagged as a breaking change when it isn't - so this is waiting...

Still waiting on the service team here?

@magodo any chance we could get this one reopened/fixed up so that we can get this merged/usable in the provider?

ping @rkmanda @tianxchen-ms - any update on this one?

Per the comment above: > There are no breaking changes. So AFAICT this PR is good to review / the build failures are misleading and this is waiting on the...

@rkmanda the `prettier` check has been fixed - checking the `modelvalidation` check, this is an existing failure, so that would need to be addressed by the Service Team outside of...