Powershell: Is changing the name of a parameter set considered breaking?

[KirkMunro]

Are parameter set names considered contractual, and therefore changing a parameter set name is considered breaking, or can they be changed as required (i.e. when moving parameters into a new base class as part of a refactoring effort performed while fixing some issues in a set of commands that share those parameters)?

The breaking change documentation does not mention parameter sets at all, and therefore I would think parameter set names are not contractual, but thought I should check first to make sure.

cc: @SteveL-MSFT

[BrucePay]

@KirkMunro Thanks for bringing this up. We decided way back in V1 that changing the name of a parameter set would officially not be considered a breaking change. But of course it's a publicly visible property so i'm sure people have taken dependencies on them. At this point, the Committee should probably review this decision/guidance and update it if necessary.

[iSazonov]

I would not want it to be a breaking change because we have already discussed that parameter binding should be enhanced to support more features (like PSMore idea and more flexible parameter set description notation).
It also seems that the addition of any new parameter may cause a redefinition of parameter sets in any cmdlet.

[SteveL-MSFT]

@PowerShell/powershell-committee reviewed this. We reaffirm that ParameterSet names are not a public api and changing them is not a breaking change. We should update the breaking change contract doc to make this apparent and explicit.