Skip to content

[AutoPR @azure-arm-cosmosdb]-generated-from-SDK Generation - JS-6150781#38137

Draft
azure-sdk wants to merge 2 commits intomainfrom
sdkauto/@azure-arm-cosmosdb-6150781
Draft

[AutoPR @azure-arm-cosmosdb]-generated-from-SDK Generation - JS-6150781#38137
azure-sdk wants to merge 2 commits intomainfrom
sdkauto/@azure-arm-cosmosdb-6150781

Conversation

@azure-sdk
Copy link
Copy Markdown
Collaborator

Configurations: 'specification/cosmos-db/resource-manager/Microsoft.DocumentDB/DocumentDB/tspconfig.yaml', API Version: 2025-11-01-preview, SDK Release Type: beta, and CommitSHA: 'c10d011902efc1bc14ae1c71bbd0cfaf59f7a8bd' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6150781 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.

…ocumentDB/DocumentDB/tspconfig.yaml', API Version: 2025-11-01-preview, SDK Release Type: beta, and CommitSHA: 'c10d011902efc1bc14ae1c71bbd0cfaf59f7a8bd' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6150781 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
@github-actions github-actions bot added the Mgmt This issue is related to a management-plane library. label Apr 14, 2026
@github-actions
Copy link
Copy Markdown

Next Steps to Merge

Only failed checks and required actions are listed below.

  • ⏳ checkenforcer: still running (waiting for all checks to complete).
  • 🔴 Draft PR: This PR is currently in draft state. Mark it as ready for review once issues are resolved.

Note: All ADO CI checks (js - pullrequest, Build, UnitTest) have passed. The two blocking items from the API review above (CHANGELOG comparison base and same api-version) require regeneration or clarification before proceeding.

Copy link
Copy Markdown

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 tool issues found in @azure/arm-cosmosdb 17.0.0-beta.3:

  1. CHANGELOG comparison baseCHANGELOG.md compares 17.0.0-beta.3 against 16.4.0 instead of the immediately preceding 17.0.0-beta.2. The generation tool did not detect the existing beta on main.
  2. Same api-version — The api-version 2025-11-01-preview introduced in this PR is identical to the one already in 17.0.0-beta.2. Per guidelines, the api-version must be strictly newer than what is already present in the package.

No public API surface design issues (naming, reserved keywords, _N suffixes) were found.

📊 Structured Report
{"agent":"mgmt-reviewer","pr":38137,"summary":"issues_found","findings":[{"file":"sdk/cosmosdb/arm-cosmosdb/CHANGELOG.md","line":4,"issueType":"tool","category":"changelog-comparison-base","description":"17.0.0-beta.3 compares with 16.4.0 instead of 17.0.0-beta.2 (the existing beta on main)"},{"file":"sdk/cosmosdb/arm-cosmosdb/metadata.json","line":3,"issueType":"tool","category":"api-version-not-newer","description":"api-version 2025-11-01-preview is the same as already present in 17.0.0-beta.2; must be strictly newer"}]}

Benchmarked by Management Release Assistant

# Release History

## 17.0.0-beta.3 (2026-04-14)
Compared with version 16.4.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Tool IssueCHANGELOG.md:4
Compared with version 16.4.0

This entry should compare with the immediately preceding published version 17.0.0-beta.2, not 16.4.0. The package was already at 17.0.0-beta.2 on the main branch before this PR. Skipping the comparison base to an older stable version suggests the generation tool did not detect the existing beta version.

Fix: Update CHANGELOG.md to say Compared with version 17.0.0-beta.2, and report this tooling behavior in the generation tool repository.

@@ -0,0 +1,869 @@
{
"apiVersions": {
"Microsoft.DocumentDB": "2025-11-01-preview"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Tool Issuemetadata.json:3
"Microsoft.DocumentDB": "2025-11-01-preview"

The api-version 2025-11-01-preview introduced in this PR is the same as the one already present in the package (17.0.0-beta.2 on main also used 2025-11-01-preview). The api-version must be strictly newer than the one already present.

Fix: Regenerate from a spec commit that targets a newer api-version, or confirm with the service team whether a new api-version is available. If this is intentional (e.g., pure TypeSpec tooling migration with no spec change), please note this in the PR description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Mgmt This issue is related to a management-plane library. refresh PR for SDK refresh

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants