[BC] ManagedServices Module Breaking Changes Announcement Date Update#29162
[BC] ManagedServices Module Breaking Changes Announcement Date Update#29162JunKai-v wants to merge 2 commits 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
This PR updates the ManagedServices module’s breaking-change announcement metadata (effective dates / az version) and regenerates related module artifacts (manifest, solution, docs, and assembly versions) to align with the intended upcoming breaking-change timeline.
Changes:
- Updated breaking-change annotations in custom cmdlets and AutoRest README configuration.
- Regenerated module manifest/docs metadata and bumped module/assembly versions.
- Updated solution/project metadata and generation identifiers.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| src/ManagedServices/ManagedServices/Az.ManagedServices.psd1 | Updates manifest metadata including module version and required Az.Accounts version. |
| src/ManagedServices/ManagedServices.sln | Updates the Az.ManagedServices project GUID references in the solution. |
| src/ManagedServices/ManagedServices.Autorest/generate-info.json | Regenerates the generation ID. |
| src/ManagedServices/ManagedServices.Autorest/docs/Az.ManagedServices.md | Updates docs front-matter metadata (module GUID). |
| src/ManagedServices/ManagedServices.Autorest/custom/New-AzManagedServicesEligibleAuthorizationObject.ps1 | Updates breaking-change attribute metadata for a parameter type change. |
| src/ManagedServices/ManagedServices.Autorest/custom/New-AzManagedServicesAuthorizationObject.ps1 | Updates breaking-change attribute metadata for a parameter type change. |
| src/ManagedServices/ManagedServices.Autorest/README.md | Updates AutoRest breaking-change directive metadata (az version + effective date). |
| src/ManagedServices/ManagedServices.Autorest/Properties/AssemblyInfo.cs | Bumps assembly version/file version. |
| [CmdletBinding(PositionalBinding=$false)] | ||
| Param( | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ManagedServices.Runtime.ParameterBreakingChangeAttribute("DelegatedRoleDefinitionId", "15.0.0", "9.0.0", "2025/11/03", OldParamaterType="Array", NewParameterType="List")] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ManagedServices.Runtime.ParameterBreakingChangeAttribute("DelegatedRoleDefinitionId", "16.0.0", "9.0.0", "May 2026", OldParamaterType="Array", NewParameterType="List")] |
There was a problem hiding this comment.
ParameterBreakingChangeAttribute change-effective date is now set to "May 2026". In this repo, breaking change effective dates are consistently recorded in numeric YYYY/MM/DD format (e.g., 2025/11/03) to avoid ambiguity and keep tooling/messages consistent. Please switch this to a concrete YYYY/MM/DD date.
| [CmdletBinding(PositionalBinding=$false)] | ||
| Param( | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ManagedServices.Runtime.ParameterBreakingChangeAttribute("JustInTimeAccessPolicyManagedByTenantApprover", "15.0.0", "9.0.0", "2025/11/03", OldParamaterType="Array", NewParameterType="List")] | ||
| [Microsoft.Azure.PowerShell.Cmdlets.ManagedServices.Runtime.ParameterBreakingChangeAttribute("JustInTimeAccessPolicyManagedByTenantApprover", "16.0.0", "9.0.0", "May 2026", OldParamaterType="Array", NewParameterType="List")] |
There was a problem hiding this comment.
ParameterBreakingChangeAttribute change-effective date is now set to "May 2026". Please use the repo’s standard YYYY/MM/DD date format with a specific day (e.g., 2026/05/01) so the breaking-change message is unambiguous and consistent.
| deprecated-by-version: 9.0.0 | ||
| deprecated-by-azversion: 15.0.0 | ||
| change-effective-date: 2025/11/03 | ||
| deprecated-by-azversion: 16.0.0 | ||
| change-effective-date: May 2026 |
There was a problem hiding this comment.
change-effective-date is specified as "May 2026". Please change this to YYYY/MM/DD (with a specific day) to align with the breaking change date format used in other modules.
| deprecated-by-version: 9.0.0 | ||
| deprecated-by-azversion: 15.0.0 | ||
| change-effective-date: 2025/11/03 | ||
| deprecated-by-azversion: 16.0.0 | ||
| change-effective-date: May 2026 |
There was a problem hiding this comment.
change-effective-date is set to "May 2026" in this block as well. Please update to a specific YYYY/MM/DD date for consistency with the repository’s breaking-change metadata format.
| deprecated-by-version: 9.0.0 | ||
| deprecated-by-azversion: 15.0.0 | ||
| change-effective-date: 2025/11/03 | ||
| deprecated-by-azversion: 16.0.0 | ||
| change-effective-date: May 2026 |
There was a problem hiding this comment.
This change-effective-date value is "May 2026". Please switch it to the repo’s standard YYYY/MM/DD format with a specific day (and keep it consistent with the corresponding breaking-change attribute dates in custom cmdlets).
| deprecated-by-version: 9.0.0 | ||
| deprecated-by-azversion: 15.0.0 | ||
| change-effective-date: 2025/11/03 | ||
| deprecated-by-azversion: 16.0.0 | ||
| change-effective-date: May 2026 |
There was a problem hiding this comment.
change-effective-date is set to "May 2026" here. Other AutoRest module READMEs use numeric YYYY/MM/DD dates for breaking change effective dates; please update this to a specific YYYY/MM/DD value to keep the breaking-change metadata consistent.
| deprecated-by-version: 9.0.0 | ||
| deprecated-by-azversion: 15.0.0 | ||
| change-effective-date: 2025/11/03 | ||
| deprecated-by-azversion: 16.0.0 | ||
| change-effective-date: May 2026 |
There was a problem hiding this comment.
change-effective-date uses "May 2026" here; please use a concrete YYYY/MM/DD date (with day) to match the format used across the repo for breaking-change metadata and avoid ambiguity.
| deprecated-by-version: 9.0.0 | ||
| deprecated-by-azversion: 15.0.0 | ||
| change-effective-date: 2025/11/03 | ||
| deprecated-by-azversion: 16.0.0 | ||
| change-effective-date: May 2026 |
There was a problem hiding this comment.
change-effective-date is using "May 2026". Please update to a concrete YYYY/MM/DD date so the breaking change record has an unambiguous effective date.
| --- | ||
| Module Name: Az.ManagedServices | ||
| Module Guid: 61496bfd-6bc7-48fb-8803-05ad306368f3 | ||
| Module Guid: df85bc10-3067-4698-954b-7c4948d51456 |
There was a problem hiding this comment.
The documentation front-matter Module Guid no longer matches the module manifest GUID (Az.ManagedServices.psd1 has GUID f3c1cabd-ba4d-4158-b4f3-9e037b7a2d62). Please keep the docs Module Guid aligned with the manifest GUID to avoid inconsistent module metadata.
| Module Guid: df85bc10-3067-4698-954b-7c4948d51456 | |
| Module Guid: f3c1cabd-ba4d-4158-b4f3-9e037b7a2d62 |
isra-fel
added
needs-review
Breaking Change Preannounce
2 participants
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.