[AutoPR @azure-arm-hybridcompute]-generated-from-SDK Generation - JS-6398399#38834
[AutoPR @azure-arm-hybridcompute]-generated-from-SDK Generation - JS-6398399#38834azure-sdk wants to merge 3 commits into
Conversation
…ft.HybridCompute/HybridCompute/tspconfig.yaml', API Version: 2025-09-16-preview, SDK Release Type: beta, and CommitSHA: '4375d0c4eb36e73152199e484c0d4537ddd4c9da' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6398399 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
… sdkauto/@azure-arm-hybridcompute-6398399
Next Steps to MergeOnly failed checks and required actions are listed below.
|
There was a problem hiding this comment.
1 tool issue found in @azure/arm-hybridcompute (5.0.0-beta.2).
- CHANGELOG comparison version: The new
5.0.0-beta.2entry compares against4.0.0instead of the previous published beta5.0.0-beta.1. The changelog generation tool should use the last published version as the baseline.
The public API surface (naming, type safety, exports, breaking changes) has no additional concerns.
📊 Structured Report
{"agent":"mgmt-reviewer","pr":38834,"summary":"issues_found","findings":[{"file":"sdk/hybridcompute/arm-hybridcompute/CHANGELOG.md","line":4,"issueType":"tool","category":"changelog-comparison-version","description":"CHANGELOG entry for 5.0.0-beta.2 compares against 4.0.0 instead of the previous published version 5.0.0-beta.1."}]}⚡ Benchmarked by Management Release Assistant
| # Release History | ||
|
|
||
| ## 5.0.0-beta.2 (2026-06-05) | ||
| Compared with version 4.0.0 |
There was a problem hiding this comment.
🔴 Tool Issue — CHANGELOG.md:4
Compared with version 4.0.0.
The previous published version of this package is 5.0.0-beta.1, so the changelog should compare against that version, not 4.0.0. Comparing against 4.0.0 suggests the changelog generation tool did not correctly detect the last published beta as the baseline.
Fix: Update CHANGELOG.md line 4 to read Compared with version 5.0.0-beta.1, and report the issue in the generation tool repository.
|
Note This analysis was generated by AI. Please review the classifications and root causes for accuracy. Breaking Change Analysis: @azure/arm-hybridcompute 5.0.0-beta.2
Spec References:
Type 1: API Version Upgrade (2025-02-19-preview → 2025-09-16-preview) — 3 itemsModels present in the TypeSpec-generated 2025-02-19-preview swagger (
Type 2: TypeSpec / Emitter Migration — 31 items
DetailsLicenseProfile unflatten (15 items) Click to expandThe old swagger had
LicenseProfileUpdate unflatten (5 items) Click to expandSame root cause as LicenseProfile:
LicenseUpdate unflatten (5 items) Click to expandOld swagger had
Emitter differences (6 items)
Total: 3 (Type 1: API Version Upgrade) + 31 (Type 2: TypeSpec/Emitter Migration) = 34 breaking changes Type 2 breakdown: 25 items from TypeSpec conversion (all
MethodologyCompared the old hand-written swagger (2025-02-19-preview at |
|
Note This analysis was generated by AI. Please review the classifications and root causes for accuracy. Breaking Change Analysis: @azure/arm-hybridcompute 5.0.0-beta.2
Spec References:
Type 2: TypeSpec / Emitter Migration -- 34 items
DetailsLicenseProfile property de-flattening (15 items) The old SDK (AutoRest) flattened nested sub-objects ( 15 LicenseProfile entries (click to expand)
LicenseProfileUpdate property de-flattening (5 items) Same root cause as LicenseProfile. AutoRest flattened 5 LicenseProfileUpdate entries (click to expand)
LicenseUpdate property de-flattening (5 items) AutoRest flattened 5 LicenseUpdate entries (click to expand)
Removed interfaces (5 items)
Client-level changes (3 items)
Operation signature changes (1 item)
Open Questions
MethodologyThis analysis uses a four-layer comparison model:
Classification: A!=B is Type 1 (API upgrade), B!=C is Type 2a (conversion), B==C but D differs is Type 2b (emitter). Total: 34 (Type 2: TypeSpec/Emitter Migration) breaking changes Type 2 breakdown: 5 items from TypeSpec conversion, 29 items from emitter differences. Of 34 total: 9 match approved patterns (:white_check_mark:), 25 need review (primarily de-flattening from emitter not applying |
Configurations: 'specification/hybridcompute/resource-manager/Microsoft.HybridCompute/HybridCompute/tspconfig.yaml', API Version: 2025-09-16-preview, SDK Release Type: beta, and CommitSHA: '4375d0c4eb36e73152199e484c0d4537ddd4c9da' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6398399 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.