[BC]Websites Module Breaking Changes Announcement Date Update#29135
[BC]Websites Module Breaking Changes Announcement Date Update#29135JiaSeng-v wants to merge 1 commit intoAzure:mainfrom
Conversation
| 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
Updates the Az.Websites module’s breaking-change preview announcement to a new target Az release/version and refreshes related generated artifacts/metadata.
Changes:
- Updated
PreviewMessage/preview-announcementtext for Websites cmdlets to reference Az v16.0.0 and a May 2026 release. - Refreshed module manifest metadata (generation timestamp, dependency version, manifest fields formatting).
- Updated ancillary generated/packaging files (solution project GUID, generate-info id, docs module guid, assembly version).
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| src/Websites/Websites/Az.Websites.psd1 | Updates manifest metadata (generation date), bumps required Az.Accounts version, and normalizes a few manifest fields. |
| src/Websites/Websites.sln | Updates the Az.Websites project GUID entry within the solution. |
| src/Websites/Websites.Autorest/generate-info.json | Regenerates the generation identifier. |
| src/Websites/Websites.Autorest/docs/Az.Websites.md | Updates the module GUID metadata in the Autorest docs header. |
| src/Websites/Websites.Autorest/custom/New-AzStaticWebApp.ps1 | Updates the breaking-change preview announcement text surfaced by the cmdlet. |
| src/Websites/Websites.Autorest/README.md | Updates Autorest directive preview-message text for breaking-change announcements. |
| src/Websites/Websites.Autorest/Properties/AssemblyInfo.cs | Bumps assembly version attributes to 3.4.2. |
| function New-AzStaticWebApp { | ||
| [Microsoft.Azure.PowerShell.Cmdlets.Websites.Runtime.PreviewMessage("**********************************************************************************************`n | ||
| * This cmdlet will undergo a breaking change in Az v15.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.
The preview message says "to be released on May 2026", which is grammatically incorrect for a month-only date. Consider changing to "to be released in May 2026" (or provide a specific day/month and keep "on").
| * 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 |
| set: | ||
| preview-announcement: | ||
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v15.0.0, to be released on November 19th 2025. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" | ||
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" |
There was a problem hiding this comment.
The preview-message text uses "to be released on May 2026" (month-only date). For consistency and correct grammar, change this to "to be released in May 2026" (or specify an exact date if you want to keep "on").
| set: | ||
| preview-announcement: | ||
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v15.0.0, to be released on November 19th 2025. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" | ||
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" |
There was a problem hiding this comment.
This second preview-message block also uses "to be released on May 2026". Please update it to "to be released in May 2026" (or specify an exact date) to match the intended wording.
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" | |
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" |
| - where: | ||
| verb: Get | ||
| subject: ContinuousWebJob|SlotContinuousWebJob|SlotTriggeredWebJob|TriggeredWebJob|TriggeredWebJobHistory | ||
| set: | ||
| preview-announcement: | ||
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v15.0.0, to be released on November 19th 2025. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" | ||
| preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************" | ||
|
|
There was a problem hiding this comment.
These preview-announcement directives are customizing the generated breaking-change message, but there’s no nearby comment explaining why the directive is needed (what behavior it’s preserving/what change is being announced). Add a short comment above each directive block describing the intent so future regeneration/maintenance is easier.
|
|
||
| # Modules that must be imported into the global environment prior to importing this module | ||
| RequiredModules = @(@{ModuleName = 'Az.Accounts'; ModuleVersion = '5.3.0'; }) | ||
| RequiredModules = @(@{ModuleName = 'Az.Accounts'; ModuleVersion = '5.3.2'; }) |
There was a problem hiding this comment.
PR title/description indicates this is only a breaking-change announcement date update, but this change also bumps the Az.Accounts dependency version (and the PR includes other regeneration/version changes). Either update the PR description/title to reflect the additional scope, or revert/split unrelated version bumps to keep the change focused.
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.