GeezerVison is showing github.com — Identify renaming a parameter set as non-breaking in the breaking cha… · PowerShell/PowerShell@c752694
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: docs/dev-process/breaking-change-contract.md +3-1Lines changed: 3 additions & 1 deletion - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -71,7 +71,9 @@ Changes to surface area or behavior that is clearly internal or non-breaking in |
71 | 71 |
|
72 | 72 | Examples: |
73 | 73 |
|
74 | | -+ Changes to internal APIs that break private reflection |
| 74 | ++ Changes to internal APIs that break private reflection. |
| 75 | ++ Changes to APIs in the `System.Management.Automation.Internal` namespace (even if they are public, they are still considered internal and subject to change). |
| 76 | ++ Renaming a parameter set (see related discussion [here](https://github.com/PowerShell/PowerShell/issues/10058)). |
75 | 77 |
|
76 | 78 | It is impossible to evolve a code base without making such changes, so we don't require up-front approval for these, but we will sometimes have to go back and |
77 | 79 | revisit such change if there's too much pain inflicted on the ecosystem through a popular app or library. |
|