You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, only named clients can be marked as "Allow breaking change". Our team would love the ability to mark anonymous clients in the conditional breaking changes section. "Allow breaking change for these clients: Marks a breaking change as safe when it only affects the following clients." We commonly query environments from our dev machines and do not identify the operation. This causes multiple approvals and pipeline reruns.
We'd like to get to a point where only named clients get the protection of schema validation.
The text was updated successfully, but these errors were encountered:
馃憢馃徎
Today, only named clients can be marked as "Allow breaking change". Our team would love the ability to mark anonymous clients in the conditional breaking changes section. "Allow breaking change for these clients: Marks a breaking change as safe when it only affects the following clients." We commonly query environments from our dev machines and do not identify the operation. This causes multiple approvals and pipeline reruns.
We'd like to get to a point where only named clients get the protection of schema validation.
The text was updated successfully, but these errors were encountered: