Merge branch 'main' into typespec-next

Author: mikeharder

.github/CODEOWNERS

@@ -134,13 +134,13 @@
 /specification/iothub/ @rkmanda
 
 # PRLabel: %KeyVault
-/specification/keyvault/resource-manager/ @vickm @chen-karen @cheathamb36 @lgonsoulin
+/specification/keyvault/resource-manager/ @vickm @chen-karen @cheathamb36 @Azure/azure-sdk-write-keyvault
 
 # PRLabel: %KeyVault
-/specification/keyvault/Security.*/ @vickm @chen-karen @cheathamb36 @lgonsoulin @heaths @chlowell
+/specification/keyvault/Security.*/ @vickm @chen-karen @cheathamb36 @Azure/azure-sdk-write-keyvault @heaths @chlowell
 
 # PRLabel: %KeyVault
-/specification/keyvault/data-plane/ @vickm @chen-karen @cheathamb36 @lgonsoulin @heaths
+/specification/keyvault/data-plane/ @vickm @chen-karen @cheathamb36 @Azure/azure-sdk-write-keyvault @heaths
 
 # PRLabel: %Logic App
 /specification/logic/ @pankajsn @tonytang-microsoft-com
@@ -292,4 +292,6 @@
 
 ## Copilot
 /.github/copilot-instructions.md @praveenkuttappan @maririos
-/.github/prompts/ @praveenkuttappan @maririos
+/.github/prompts/                @praveenkuttappan @maririos
+/.github/instructions/           @praveenkuttappan @maririos
+/.github/chatmodes/              @praveenkuttappan @maririos

.github/copilot-instructions.md

@@ -184,7 +184,7 @@ from the list of paths. If user does not have a TypeSpec project, then prompt us
     - Confirm with the user if they want to change the repo owner or target branch, and prompt for new values if needed.
 
 6. **Exclusions**:
-    - Exclude changes in `.github` and `.vscode` folders from API spec and SDK pull requests.
+    - Exclude changes to the `.gitignore` file and contents within the `.github` and `.vscode` folders from API spec and SDK pull requests.
 
 7. **Working Branch Rule**:
     - Ensure the TypeSpec project repository and the current working repository are not on the `main` branch:
@@ -201,7 +201,7 @@ from the list of paths. If user does not have a TypeSpec project, then prompt us
 By following these rules, the SDK release process will remain clear, structured, and user-friendly.
 
 ## Steps to generate SDK from TypeSpec API specification
-Follow `/typespec-to-sdk` prompt to generate and release SDK from TypeSpec API specification. The process is divided into several steps, each with specific actions to ensure a smooth SDK generation and release process.
+Follow [typespec to sdk](.\prompts\typespec-to-sdk.prompt.md) to generate and release SDK from TypeSpec API specification. The process is divided into several steps, each with specific actions to ensure a smooth SDK generation and release process.
 Do not skip the step that choose SDK generation method to ensure the user selects the appropriate method for SDK generation, either locally or using the SDK generation pipeline. Do not repeat the steps.
 
 1. **Identify TypeSpec Project**: Locate the TypeSpec project root path by checking for `tspconfig.yaml` or `main.tsp` files.
@@ -210,12 +210,12 @@ Do not skip the step that choose SDK generation method to ensure the user select
 4. **Review and Commit Changes**: Stage and commit TypeSpec modifications, ensuring the current branch is not "main". Do not create pull request yet.
 5. **Create Specification Pull Request**: Create a pull request for TypeSpec changes if not already created. This is required only if there are TypeSpec changes in current branch.
 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.
+7. **Generate SDKs via Pipeline**:  Generate SDKs using [run sdk gen pipeline](.\prompts\run-sdk-gen-pipeline.prompt.md), 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**: To create a release plan refer to #file:.\prompts\create-release-plan.prompt.md
+9. **Create a release plan**: To create a release plan refer to [create release plan](.\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.
 
 
 ## Release readiness of SDK and information about the release pipeline
-Run `/check-package-readiness` prompt to check the release readiness of an SDK package. This prompt will collect the required information from the user, execute the readiness check, and present the results.
+Run [check package readiness](.\prompts\check-package-readiness.prompt.md) to check the release readiness of an SDK package. This prompt will collect the required information from the user, execute the readiness check, and present the results.

.github/dependabot.yml

@@ -1,13 +1,10 @@
 version: 2
 updates:
-  # For monorepos, only the root folder should be listed (not the sub-folders).
-  # We may also need to set "versioning-strategy" to "increase" rather than "increase-if-necessary",
-  # to update both package.json and package-lock.json files.  In our case, we don't really care
-  # if the package.json files are updated or not, just that package-lock.json is update.
-  # https://github.com/dependabot/dependabot-core/issues/4993#issuecomment-1289133027
   - package-ecosystem: "npm"
     directories:
       - "/"
+      - "/eng/tools"
+      - "/eng/tools/**"
     schedule:
       interval: "daily"
     ignore:
@@ -41,8 +38,7 @@ updates:
       eslint:
         patterns:
           - "*eslint*"
-    # I prefer "increase-if-necessary", but I believe we may need to use "increase" since we're a monorepo
-    versioning-strategy: increase
+    versioning-strategy: increase-if-necessary
   - package-ecosystem: "npm"
     directories:
       - "/.github"
@@ -59,9 +55,10 @@ updates:
       - dependency-name: "typescript"
       # Points to "github:actions/github-script" since package isn't published to npmjs
       - dependency-name: "@types/github-script"
+      # Stay on ^7 until ^10 increases in adoption
+      - dependency-name: "cross-env"
     groups:
       eslint:
         patterns:
           - "*eslint*"
-    # I prefer "increase-if-necessary", but we should align with the root package.json
-    versioning-strategy: increase
+    versioning-strategy: increase-if-necessary

.github/eslint.config.js

@@ -1,5 +1,8 @@
-import pluginJs from "@eslint/js";
+import eslint from "@eslint/js";
 import globals from "globals";
+import tseslint from "typescript-eslint";
 
 /** @type {import('eslint').Linter.Config[]} */
-export default [{ languageOptions: { globals: globals.node } }, pluginJs.configs.recommended];
+export default tseslint.config(eslint.configs.recommended, tseslint.configs.recommended, {
+  languageOptions: { globals: globals.node },
+});