add breaking change message for fd #28747
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull Request Overview
This PR adds breaking change metadata for the Azure Front Door PowerShell module, documenting the migration from legacy SDK-based cmdlets to AutoRest-generated cmdlets. The changes declare deprecated output types and parameter types that will be removed in version 5.0.0 (Az 14.0.0), with replacements specified for each deprecated type.
Key Changes:
- Adds breaking change directives for output type changes across 20+ cmdlet subjects
- Adds breaking change directives for parameter type changes across 50+ cmdlet parameters
- Sets deprecation timeline (version 5.0.0, Az 14.0.0, effective 2025/5/19)
- Migrates from
Microsoft.Azure.Commands.FrontDoor.Models.*types toMicrosoft.Azure.PowerShell.Cmdlets.FrontDoor.Models.*types
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run azure-powershell - powershell-core |
|
Azure Pipelines successfully started running 1 pipeline(s). |
isra-fel
added
the
Breaking Change Preannounce
This was referenced Oct 27, 2025
added 2 commits
October 28, 2025 10:31
…/azure-powershell into beaking-change-message-fd
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
isra-fel
approved these changes
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.