Merge branch 'main' into applicationinsights-convert-singleapi

Author: msyyc

.github/.prettierrc.yaml

@@ -1,5 +1,8 @@
 # Keep in sync with eng/tools/.prettierrc.yaml
 
+plugins:
+  - prettier-plugin-organize-imports
+
 # Aligned with microsoft/typespec
 printWidth: 100
 

.github/CODEOWNERS

@@ -67,7 +67,7 @@
 # PRLabel: %Compute
 /specification/compute/ @bilaakpan-ms @sandido @dkulkarni-ms @haagha @MS-syh2qs @grizzlytheodore @mabhard @danielli90 @smotwani @ppatwa @vikramd-ms @yunusm @ZhidongPeng @nkuchta @maheshnemichand @najams @changov
 
-/specification/consumption/ @kjeur @panda-wang
+/specification/consumption/ @arusing @micahbresette
 
 # PRLabel: %Container Instances
 /specification/containerinstance/ @novinc

.github/copilot-instructions.md

@@ -212,7 +212,7 @@ Do not skip the step that choose SDK generation method to ensure the user select
 6. **Choose SDK Generation Method**: Determine how to generate SDKs (locally or via pipeline). Only Python is supported for local SDK generation at this time.
 7. **Generate SDKs via Pipeline**:  Generate SDKs using `/run-sdk-gen-pipeline` prompt, monitor the pipeline status and displaying generated SDK PR links.
 8. **Show generated SDK PR**: Display the generated SDK pull request links for review.
-9. **Create a release plan**: Create a release plan for the generated SDKs using spec pull request.
+9. **Create a release plan**: To create a release plan refer to #file:.\prompts\create-release-plan.prompt.md
 10. **Prompt user to change spec pull request to ready for review from draft status**: Update spec pull request to change it to ready for review.
 11. **Release package**: Release the SDK package using `ReleaseSdkPackage` tool.
 

.github/dependabot.yml

@@ -41,8 +41,8 @@ updates:
       eslint:
         patterns:
           - "*eslint*"
-    # Leave the constraint if the original constraint allows the new version, otherwise, bump the constraint.
-    versioning-strategy: increase-if-necessary
+    # I prefer "increase-if-necessary", but I believe we may need to use "increase" since we're a monorepo
+    versioning-strategy: increase
   - package-ecosystem: "npm"
     directories:
       - "/.github"
@@ -63,5 +63,5 @@ updates:
       eslint:
         patterns:
           - "*eslint*"
-    # Leave the constraint if the original constraint allows the new version, otherwise, bump the constraint.
-    versioning-strategy: increase-if-necessary
+    # I prefer "increase-if-necessary", but we should align with the root package.json
+    versioning-strategy: increase

.github/matchers/actionlint.json

@@ -0,0 +1,17 @@
+{
+  "problemMatcher": [
+    {
+      "owner": "actionlint",
+      "pattern": [
+        {
+          "regexp": "^(?:\\x1b\\[\\d+m)?(.+?)(?:\\x1b\\[\\d+m)*:(?:\\x1b\\[\\d+m)*(\\d+)(?:\\x1b\\[\\d+m)*:(?:\\x1b\\[\\d+m)*(\\d+)(?:\\x1b\\[\\d+m)*: (?:\\x1b\\[\\d+m)*(.+?)(?:\\x1b\\[\\d+m)* \\[(.+?)\\]$",
+          "file": 1,
+          "line": 2,
+          "column": 3,
+          "message": 4,
+          "code": 5
+        }
+      ]
+    }
+  ]
+}

.github/package-lock.json

@@ -6,10 +6,10 @@
     "dependencies2": "All runtime and dev dependencies in this file, must be a superset of shared/package.json"
   },
   "dependencies": {
-    "@apidevtools/json-schema-ref-parser": "^14.1.0",
+    "@apidevtools/json-schema-ref-parser": "^14.1.1",
     "debug": "^4.4.0",
     "js-yaml": "^4.1.0",
-    "marked": "^16.0.0",
+    "marked": "^16.1.1",
     "markdown-table": "^3.0.4",
     "simple-git": "^3.27.0",
     "zod": "^4.0.2"
@@ -28,6 +28,7 @@
     "eslint": "^9.22.0",
     "globals": "^16.0.0",
     "prettier": "~3.5.3",
+    "prettier-plugin-organize-imports": "^4.2.0",
     "semver": "^7.7.1",
     "typescript": "~5.8.2",
     "vitest": "^3.0.7"

.github/package.json

@@ -20,8 +20,7 @@ Follow these steps in order to create or manage a release plan for an API specif
 - If no release plan exists, proceed to Step 3
 
 ## Step 3: Gather Release Plan Information
-Collect the following required information from the user. Do not use non GUID valid for product and service tree Id. Do not create release plan with temporary values.
-Do not assume or use default for service tree Id and product service tree Id. Always show the values to user and ask them to confirm it's a valid value in service tree.
+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.
 If any details are missing, prompt the user accordingly:
 
 - **API Lifecycle Stage**: Must be one of:

.github/prompts/create-release-plan.prompt.md

@@ -19,6 +19,7 @@
     "./spec-model": "./src/spec-model.js",
     "./swagger": "./src/swagger.js",
     "./tag": "./src/tag.js",
+    "./simple-git": "./src/simple-git.js",
     "./test/examples": "./test/examples.js"
   },
   "bin": {
@@ -29,10 +30,10 @@
     "dependencies2": "All runtime and dev dependencies in this file, must be a subset of ../package.json"
   },
   "dependencies": {
-    "@apidevtools/json-schema-ref-parser": "^14.1.0",
+    "@apidevtools/json-schema-ref-parser": "^14.1.1",
     "debug": "^4.4.0",
     "js-yaml": "^4.1.0",
-    "marked": "^16.0.0",
+    "marked": "^16.1.1",
     "simple-git": "^3.27.0"
   },
   "devDependencies": {
@@ -46,6 +47,7 @@
     "eslint": "^9.22.0",
     "globals": "^16.0.0",
     "prettier": "~3.5.3",
+    "prettier-plugin-organize-imports": "^4.2.0",
     "semver": "^7.7.1",
     "typescript": "~5.8.2",
     "vitest": "^3.0.7"