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
Copy file name to clipboardExpand all lines: docs/Agent User Guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ To see the results go to Validation Results step. For each service for which a s
42
42
">
43
43
<div>
44
44
<li>Breaking change is a change that breaks backward compatibility with the previous version of API. For example, deleting an operation, adding a required parameter or changing the type of a parameter are breaking changes.</li>
45
-
<li>Risky change is a change that breaks backward compatibility according to the rules:</li>
45
+
<li>A change requiring attention is a change that breaks backward compatibility according to the rules:</li>
46
46
<ul>
47
47
<li>operation or entity in the operation was annotated as deprecated in at least two previous consecutive releases and then it was deleted
Copy file name to clipboardExpand all lines: docs/Portal User Guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -697,7 +697,7 @@ If during package version publication, you specified a previous release version,
697
697
698
698
- Breaking – Breaking change is a change that breaks backward compatibility with the previous version of API.
699
699
For example, deleting an operation, adding a required parameter or changing the type of a parameter are breaking changes.
700
-
-Risky – Risky change is a change that breaks backward compatibility according to the rules:
700
+
-Requires Attention – A change requiring attention is a change that breaks backward compatibility according to the rules:
701
701
- operation or entity in the operation was annotated as deprecated in at least two previous consecutive releases and then it was deleted
702
702
- operation is marked as no-BWC
703
703
- Deprecated – Deprecating change is a change that annotates an operation, parameter or schema as deprecated. Removing a "deprecated" annotation is also considered a deprecating change.
[BREAKING_CHANGE_SEVERITY]: {text: 'Breaking change is a change that breaks backward compatibility with the previous version of API. For example, deleting an operation, adding a required parameter or changing type of a parameter are breaking changes.'},
66
75
[SEMI_BREAKING_CHANGE_SEVERITY]: {
67
-
text: 'Risky change is a change that breaks backward compatibility according to the rules:',
76
+
text: 'A change requiring attention is a change that breaks backward compatibility according to the rules:',
68
77
options: ['operation was annotated as deprecated in at least two previous consecutive releases and then it was deleted','operation is marked as no-BWC'],
69
78
},
70
79
[DEPRECATED_CHANGE_SEVERITY]: {text: 'Deprecating change is a change that annotates an operation, parameter or schema as deprecated. Removing a "deprecated" annotation is also considered a deprecating change.'},
0 commit comments