Merge branch 'main' of https://github.com/Azure/azure-rest-api-specs into edge-actions-api-2025-12-01-preview

Author: Danny Tundwe (from Dev Box)

.github/CODEOWNERS

@@ -150,13 +150,13 @@
 /specification/iothub/ @marcodalessandro @riteshrao
 
 # PRLabel: %KeyVault
-/specification/keyvault/resource-manager/ @vickm @chen-karen @cheathamb36 @Azure/azure-sdk-write-keyvault
+/specification/keyvault/resource-manager/ @chen-karen @Azure/azure-sdk-write-keyvault
 
 # PRLabel: %KeyVault
-/specification/keyvault/Security.*/ @vickm @chen-karen @cheathamb36 @Azure/azure-sdk-write-keyvault @heaths @chlowell
+/specification/keyvault/Security.*/ @chen-karen @Azure/azure-sdk-write-keyvault @heaths
 
 # PRLabel: %KeyVault
-/specification/keyvault/data-plane/ @vickm @chen-karen @cheathamb36 @Azure/azure-sdk-write-keyvault @heaths
+/specification/keyvault/data-plane/ @chen-karen @Azure/azure-sdk-write-keyvault @heaths
 
 # PRLabel: %Logic App
 /specification/logic/ @pankajsn @tonytang-microsoft-com
@@ -238,7 +238,8 @@
 /specification/servicebus/ @v-ajnava @dsouzaarun @damodaravadhani
 
 # PRLabel: %Service Fabric
-/specification/servicefabric/ @juhacket @samedder
+/specification/servicefabric/ @a-santamaria @iliu816
+/specification/servicefabricmanagedclusters/ @a-santamaria @iliu816
 
 # PRLabel: %SQL
 /specification/sql/ @jamestao @ericshape @jeremyfrosti @mitesh-pv @achyuth-ms

.github/package-lock.json

@@ -9,7 +9,7 @@
     "@apidevtools/json-schema-ref-parser": "^14.2.1",
     "debug": "^4.4.3",
     "js-yaml": "^4.1.0",
-    "marked": "^16.3.0",
+    "marked": "^17.0.0",
     "markdown-table": "^3.0.4",
     "simple-git": "^3.27.0",
     "zod": "^4.1.11"

.github/package.json

@@ -37,7 +37,7 @@
     "@apidevtools/json-schema-ref-parser": "^14.2.1",
     "debug": "^4.4.3",
     "js-yaml": "^4.1.0",
-    "marked": "^16.3.0",
+    "marked": "^17.0.0",
     "simple-git": "^3.27.0",
     "zod": "^4.1.11"
   },

.github/shared/package-lock.json

@@ -1,7 +1,8 @@
-> **Important Note for LLM**
-> Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
-> All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.
-> Only provide release plan details such as **Release Plan Link** and **Release Plan ID** to the user
+> **CRITICAL INSTRUCTIONS FOR LLM**
+> 1. Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
+> 2. All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.
+> 3. Only provide release plan details such as **Release Plan Link** and **Release Plan ID** to the user
+> 4. Always check the `NextSteps` field in the tool response and follow any additional prompts provided. Do NOT proceed to other steps until the NextSteps are completed.
 
 # Release Plan Creation Process
 Your goal is to create a valid release plan. You must prompt user to provide all required information and all input must match the format and requirement mentioned in step 3 below.
@@ -12,12 +13,14 @@ Follow these steps in order to create or manage a release plan for an API specif
 - If no pull request is available, prompt the user to provide the API spec pull request link
 - Validate that the provided pull request link is accessible and valid
 
-## Step 2: Check Existing Release Plan
-- Use `azsdk_get_release_plan_for_spec_pr` to check if a release plan already exists for the API spec pull request
-- If a release plan exists:
-    - Display the existing release plan details to the user
-    - Skip to Step 5 (Link SDK Pull Requests)
-- If no release plan exists, proceed to Step 3
+## Step 2: Check for Existing Release Plan
+- Ask the user if they already have an existing release plan
+- If they confirm:
+    - Query the existing release plan using either:
+        - The release plan number, or
+        - The API spec pull request link
+    - Display the existing release plan details (Release Plan ID, status, associated languages, SDK PRs).
+- If no existing release plan is found, continue to Step 3 to gather required details for creating a new one. 
 
 ## Step 3: Gather Release Plan Information
 Collect the following required information from the user. Do not create a release plan with temporary values. Confirm the values with the user before proceeding to create the release plan.
@@ -35,6 +38,7 @@ If any details are missing, prompt the user accordingly:
 - If the user doesn't know the required details, direct them to create a release plan using the release planner
 - Provide this resource: [Release Plan Creation Guide](https://eng.ms/docs/products/azure-developer-experience/plan/release-plan-create)
 - Once all information is gathered, use `azsdk_create_release_plan` to create the release plan
+- If existing release plans are found, extract and display key information: Release Plan ID, status, associated languages, SDK PRs
 - Display the newly created release plan details to the user for confirmation
 - Refer to #file:sdk-details-in-release-plan.instructions.md to identify languages configured in the TypeSpec project and add them to the release plan
 

.github/shared/package.json

@@ -3,18 +3,17 @@ description: 'Verify Setup'
 ---
 
 ## Goal
-This tool verifies the developer's environment for SDK development and release tasks. It returns what requirements are missing for the specified languages and repo.
+This tool verifies the developer's environment for SDK development and release tasks. It returns what requirements are missing for the specified languages and repo, or success if all requirements are satisfied.
 
 Your goal is to identify the project repo root, and pass in the `packagePath` to the Verify Setup tool. For a language repo, pass in the language of the repo.
 
 ## Examples
 - in `azure-sdk-for-js`, run `azsdk_verify_setup` with `(langs=javascript, packagePath=<path>/azure-sdk-for-js)`.
-- in `azure-sdk-for-python`, run `azsdk_verify_setup` with `(langs=python, packagePath=<path>/azure-sdk-for-python, venvPath=<path-to-venv>)`.
 
 ## Parameter Requirements
-WHENEVER Python is included in `langs`, BEFORE RUNNING `azsdk_verify_setup`, you MUST ASK THE USER TO SPECIFY WHICH virtual environment they want to check. DO NOT ASSUME THE VENV WITHOUT ASKING THE USER. After obtaining the `venvPath`, you can run the tool.
-
-The user can specify multiple languages to check. If the user wants to check all languages, pass in ALL supported languages and STILL ASK for a `venvPath`. Passing in no languages will only check the core requirements.
+The user can specify multiple languages to check. If the user wants to check all languages, pass in ALL supported languages. Passing in no languages will only check the core requirements.
 
 ## Output
-Display results in a user-friendly and concise format, highlighting any missing dependencies that need to be addressed.
+Display results in a user-friendly and concise format, highlighting any missing dependencies that need to be addressed and how to resolve them.
+
+WHENEVER Python related requirements fail, ALWAYS ASK the user if they have set the `AZSDKTOOLS_PYTHON_VENV_PATH` system environment variable to their desired virtual environment. This tool can only check requirements in the venv path specified by that environment variable.

eng/common/instructions/azsdk-tools/create-release-plan.instructions.md

@@ -530,6 +530,8 @@ foreach ($url in $urls) {
 
 LogGroupStart "Link checking details"
 
+$originalcheckLinkGuidance = $checkLinkGuidance
+
 while ($pageUrisToCheck.Count -ne 0)
 {
   $pageUri = $pageUrisToCheck.Dequeue();
@@ -538,6 +540,11 @@ while ($pageUrisToCheck.Count -ne 0)
     if ($checkedPages.ContainsKey($pageUri)) { continue }
     $checkedPages[$pageUri] = $true;
 
+    # copilot instructions require the use of relative links which is against our general guidance
+    # but we mainly care about those guidelines for docs publishing and not copilot instructions
+    # so we can disable the guidelines while validating copilot instruction files.
+    if ($pageUri -match "instructions.md$") { $checkLinkGuidance = $false }
+
     [string[]] $linkUris = GetLinks $pageUri
     Write-Host "Checking $($linkUris.Count) links found on page $pageUri";
     $badLinksPerPage = @();
@@ -561,6 +568,8 @@ while ($pageUrisToCheck.Count -ne 0)
   } catch {
     Write-Host "Exception encountered while processing pageUri $pageUri : $($_.Exception)"
     throw
+  } finally {
+    $checkLinkGuidance = $originalcheckLinkGuidance
   }
 }
 

eng/common/instructions/azsdk-tools/verify-setup.instructions.md

@@ -27,7 +27,7 @@
     "autorest": "^3.7.2",
     "change-case": "^5.4.4",
     "deep-eql": "^5.0.2",
-    "marked": "^16.3.0"
+    "marked": "^17.0.0"
   },
   "devDependencies": {
     "@types/deep-eql": "^4.0.2",