[BC]MySQL Update Release Date to May 2026#29120
Conversation
JiaSeng-v
added
Contains Breaking Change
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
|
To the author of the pull request, |
There was a problem hiding this comment.
Pull request overview
This PR updates the Az.MySql module to postpone the breaking change release date from November 19th, 2025 to May 2026. The changes were generated by AutoRest to align the code with the already-updated ChangeLog.md for version 1.5.1. This is a standard module regeneration that updates breaking change preview messages, module metadata, and auto-generated identifiers.
Changes:
- Updated breaking change preview messages across 11 cmdlet files from "November 19th 2025" to "May 2026"
- Incremented assembly version from 1.5.0 to 1.5.1
- Updated Az.Accounts dependency from 5.3.1 to 5.3.2
- Regenerated module metadata (GUIDs, generated date, generate_Id)
Reviewed changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
| Az.MySql.psd1 | Updated module manifest with new generated date (1/30/2026), Az.Accounts 5.3.2 dependency, and minor formatting improvements |
| MySql.sln | Regenerated solution file with updated project GUID for Az.MySql AutoRest project |
| generate-info.json | Updated generate_Id for the AutoRest regeneration |
| Az.MySql.md | Updated module documentation GUID (auto-regenerated) |
| Update-AzMySqlFlexibleServerFirewallRule.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Update-AzMySqlFlexibleServerConfiguration.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Update-AzMySqlFlexibleServer.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Test-AzMySqlFlexibleServerConnect.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Restore-AzMySqlFlexibleServer_PointInTimeRestore.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Restore-AzMySqlFlexibleServer_GeoRestore.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| New-AzMySqlFlexibleServerReplica.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| New-AzMySqlFlexibleServerFirewallRule.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| New-AzMySqlFlexibleServer.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Get-AzMySqlFlexibleServerLocationBasedCapability.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| Get-AzMySqlFlexibleServerConnectionString.ps1 | Updated breaking change message from November 19th 2025 to May 2026 |
| README.md | Updated AutoRest directive preview-message from "Az v15.0.0, to be released in May 2026" to "Az v16.0.0, to be released in May 2026" |
| AssemblyInfo.cs | Incremented assembly version from 1.5.0 to 1.5.1 |
| [CmdletBinding(DefaultParameterSetName='UpdateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [CmdletBinding(DefaultParameterSetName='UpdateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [CmdletBinding(DefaultParameterSetName='UpdateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Restore a server from an existing backup using GeoRestore')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Creates a new MySQL flexible server.')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Test out the connection to the database server')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Restore a server from an existing backup')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Creates a new replica from an existing database.')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [CmdletBinding(DefaultParameterSetName='CreateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
| [CmdletBinding(DefaultParameterSetName='Get', PositionalBinding=$false)] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n | ||
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n |
There was a problem hiding this comment.
Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n | |
| * This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n |
1 participant
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.