Repo sync for protected CLA branch

.github/workflows/stale-issues.yml

@@ -19,7 +19,7 @@ jobs:
       pull-requests: write  # for actions/stale to close stale PRs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v5
+      - uses: actions/stale@v6
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           stale-issue-message: 'Thanks for sharing your feedback. We apologize for our delayed response. Due to the sheer volume of feedback in our repo, we have decided to prioritize the newest issues and are automatically closing our oldest issues with an Issues bot. If you believe your feedback is still actionable, then either respond directly in this issue or open a new documentation issue and we’ll review. If no activity occurs in the next 14 days, this issue will be closed.'

.github/workflows/stale.yml

@@ -13,7 +13,7 @@ jobs:
       pull-requests: write
 
     steps:
-    - uses: actions/stale@v5.1.1
+    - uses: actions/stale@v6
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
         days-before-pr-stale: 14

docs/extensibility/how-to-use-the-activity-log.md

@@ -54,6 +54,8 @@ VSPackages can write messages to the activity log. This feature is especially us
    ```
    Called for: Company.MyApp.MyAppPackage ...
    ```
+## Troubleshooting Import/Export Issues in Editor Extensions: Access the MEF Composition Error Log
+When writing an editor-based extension, you may experience issues if you try to import something that doesn't exist in the current VS install, or if you incorrectly author your import or export.  The primary way to find and address these issues is to reference the **Managed Extensibility Framework (MEF) Composition Error Log**, stored at *%localappdata%\Microsoft\VisualStudio[yourVSVersion]\ComponentModelCache\Microsoft.VisualStudio.Default.err*.  To learn more about using MEF in your extensions, check out [this documentation](../extensibility/managed-extensibility-framework-in-the-editor.md).
 
 ## Robust programming
 

docs/extensibility/inside-the-editor.md

@@ -317,6 +317,9 @@ IntelliSense supports statement completion, signature help (also known as parame
 
 Statement completion provides pop-up lists of potential completions for method names, XML elements, and other coding or markup elements. In general, a user gesture invokes a completion session. The session displays the list of potential completions, and the user can select one or dismiss the list. The <xref:Microsoft.VisualStudio.Language.Intellisense.ICompletionBroker> is responsible for creating and triggering the <xref:Microsoft.VisualStudio.Language.Intellisense.ICompletionSession>. The <xref:Microsoft.VisualStudio.Language.Intellisense.ICompletionSource> computes the <xref:Microsoft.VisualStudio.Language.Intellisense.CompletionSet> of completion items for the session.
 
+## Troubleshooting Import/Export Issues: Access the MEF Composition Error Log 
+You may experience issues if you try to import something that doesn't exist in the current VS install, or if you incorrectly author your import or export.  The primary way to find and address these issues is to reference the **Managed Extensibility Framework (MEF) Composition Error Log**, stored at *%localappdata%\Microsoft\VisualStudio[yourVSVersion]\ComponentModelCache\Microsoft.VisualStudio.Default.err*.
+
 ## See also
 
 - [Language service and editor extension points](../extensibility/language-service-and-editor-extension-points.md)

docs/extensibility/managed-extensibility-framework-in-the-editor.md

@@ -75,6 +75,8 @@ public AdornmentLayerDefinition scarletLayerDefinition;
 [Import]
 internal IClassificationTypeRegistryService ClassificationRegistry;
 ```
+## Troubleshooting Import/Export Issues: Access the MEF Composition Error Log
+You may experience issues if you try to import something that doesn't exist in the current VS install, or if you incorrectly author your import or export.  The primary way to find and address these issues is to reference the **Managed Extensibility Framework (MEF) Composition Error Log**, stored at *%localappdata%\Microsoft\VisualStudio[yourVSVersion]\ComponentModelCache\Microsoft.VisualStudio.Default.err*.
 
 ## Get editor functionality from a MEF component part
  If your existing code is a MEF component part, you can use MEF metadata to consume editor component parts.