Service Fabric Announce breaking changes

[mwesigwaguma]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

[VeryEarly]

please read comments from this old PR: #25070
and you have missed the window for breaking change announcement, please targeting breaking changes next year

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

[github-actions]

‼️ DO NOT MERGE THIS PR ‼️
This PR was labeled "Do Not Merge" because it contains code change that cannot be merged. Please contact the reviewer for more information.

[mwesigwaguma]

please read comments from this old PR: #25070 and you have missed the window for breaking change announcement, please targeting breaking changes next year

hey @VeryEarly, can I release out of band preview version for now ?

[Nickcandy]

Apologies @mwesigwaguma, the OOB release process only applies to regular releases. Any breaking changes can only be introduced during a major release.

[VeryEarly]

please read comments from this old PR: #25070 and you have missed the window for breaking change announcement, please targeting breaking changes next year

hey @VeryEarly, can I release out of band preview version for now ?

preview version is acceptable, we can do preview release for it and you can make a proper breaking change announcement after ignite and target next build event.

[mwesigwaguma]

please read comments from this old PR: #25070 and you have missed the window for breaking change announcement, please targeting breaking changes next year

hey @VeryEarly, can I release out of band preview version for now ?

preview version is acceptable, we can do preview release for it and you can make a proper breaking change announcement after ignite and target next build event.

okay, I'll put up a PR against Az.ServiceFabric-preview branch

[mwesigwaguma]

please read comments from this old PR: #25070 and you have missed the window for breaking change announcement, please targeting breaking changes next year

hey @VeryEarly, can I release out of band preview version for now ?

preview version is acceptable, we can do preview release for it and you can make a proper breaking change announcement after ignite and target next build event.

okay, I'll put up a PR against Az.ServiceFabric-preview branch

Put up this PR for preview version #26445