Release 0.6.2

.devcontainer/devcontainer.json

@@ -0,0 +1,39 @@
+{
+  "name": "Node.js 20 Workspace",
+  "image": "mcr.microsoft.com/devcontainers/javascript-node:20",
+
+  "hostRequirements": {
+    "cpus": 4
+  },
+
+  // Lifecycle commands
+  "onCreateCommand": "npm install",
+  "updateContentCommand": "if git diff --name-only HEAD~1 HEAD | grep -E 'package(-lock)?\\.json'; then npm install; fi && npm run build",
+
+  "forwardPorts": [3000],
+  "portsAttributes": {
+    "3000": {
+      "label": "Development Server",
+      "onAutoForward": "notify"
+    }
+  },
+
+  "customizations": {
+    "vscode": {
+      "extensions": [
+        "dbaeumer.vscode-eslint",
+        "mike-lischke.vscode-antlr4",
+        "amodio.tsl-problem-matcher",
+        "Orta.vscode-jest",
+        "esbenp.prettier-vscode"
+      ],
+      "settings": {
+        "editor.formatOnSave": true,
+        "eslint.enable": true
+      }
+    }
+  },
+
+  // Cache node_modules between prebuilds
+  "mounts": ["source=node_modules-cache,target=/workspace/node_modules,type=volume"]
+}

.github/copilot-instructions.md

@@ -371,6 +371,152 @@ export async function yourCommand(context: IActionContext, targetItem: SomeItem)
 }
 ```
 
+### Wizard Back Navigation and Context Persistence
+
+When users navigate back in a wizard (via `GoBackError`), the `AzureWizard` framework resets context properties. Understanding this behavior is critical for proper wizard implementation.
+
+#### How AzureWizard Handles Back Navigation
+
+When a step throws `GoBackError`, the wizard:
+
+1. Pops steps from the finished stack until finding the previous prompted step
+2. **Resets context properties** to what existed before that step's `prompt()` ran
+3. Re-runs the step's `prompt()` method
+
+**Critical Implementation Detail**: Before each step's `prompt()` runs, the wizard captures `propertiesBeforePrompt`:
+
+```javascript
+// From AzureWizard.js - this runs for EACH step before prompt()
+step.propertiesBeforePrompt = Object.keys(this._context).filter((k) => !isNullOrUndefined(this._context[k])); // Only non-null/undefined values!
+```
+
+When going back, properties NOT in `propertiesBeforePrompt` are set to `undefined`:
+
+```javascript
+// From AzureWizard.js goBack() method
+for (const key of Object.keys(this._context)) {
+  if (!step.propertiesBeforePrompt.find((p) => p === key)) {
+    this._context[key] = undefined; // Property gets cleared!
+  }
+}
+```
+
+#### Making Context Properties Survive Back Navigation
+
+To ensure a context property survives when users navigate back, you must initialize it with a **non-null, non-undefined value** in the wizard context creation:
+
+```typescript
+// ❌ Bad - Property will be cleared on back navigation
+const wizardContext: MyWizardContext = {
+  ...context,
+  cachedData: undefined, // undefined is filtered out of propertiesBeforePrompt!
+};
+
+// ❌ Bad - Property not initialized, same problem
+const wizardContext: MyWizardContext = {
+  ...context,
+  // cachedData not set - will be undefined
+};
+
+// ✅ Good - Property will survive back navigation (using empty array)
+const wizardContext: MyWizardContext = {
+  ...context,
+  cachedData: [], // Empty array is not null/undefined, captured in propertiesBeforePrompt
+};
+
+// ✅ Good - Property will survive back navigation (using empty object)
+const wizardContext: MyWizardContext = {
+  ...context,
+  cachedConfig: {}, // Empty object is not null/undefined
+};
+
+// ✅ Good - Property will survive back navigation (using empty string)
+const wizardContext: MyWizardContext = {
+  ...context,
+  cachedId: '', // Empty string is not null/undefined
+};
+
+// ✅ Good - Property will survive back navigation (using zero)
+const wizardContext: MyWizardContext = {
+  ...context,
+  retryCount: 0, // Zero is not null/undefined
+};
+
+// ✅ Good - Property will survive back navigation (using false)
+const wizardContext: MyWizardContext = {
+  ...context,
+  hasBeenValidated: false, // false is not null/undefined
+};
+```
+
+#### Pattern for Cached Data with Back Navigation Support
+
+When you need to cache expensive data (like API calls) that should survive back navigation:
+
+1. **Context Interface**: Make the property required with a non-nullable type
+
+```typescript
+export interface MyWizardContext extends IActionContext {
+  // Required - initialized with non-null/undefined value to survive back navigation
+  cachedItems: CachedItem[];
+
+  // Optional - user selections that may be cleared
+  selectedItem?: SomeItem;
+}
+```
+
+2. **Wizard Initialization**: Initialize with a non-null/undefined value
+
+```typescript
+const wizardContext: MyWizardContext = {
+  ...context,
+  cachedItems: [], // Any non-null/undefined value survives back navigation
+};
+```
+
+3. **Step Implementation**: Check appropriately for the initial value
+
+```typescript
+public async prompt(context: MyWizardContext): Promise<void> {
+  const getQuickPickItems = async () => {
+    // Check for initial empty value (array uses .length, string uses === '', etc.)
+    if (context.cachedItems.length === 0) {
+      context.cachedItems = await this.fetchExpensiveData();
+    }
+    return context.cachedItems.map(item => ({ label: item.name }));
+  };
+
+  await context.ui.showQuickPick(getQuickPickItems(), { /* options */ });
+}
+```
+
+4. **Clearing Cache**: Reset to the initial non-null/undefined value
+
+```typescript
+// When you need to invalidate the cache (e.g., after a mutation)
+context.cachedItems = []; // Reset to initial value, not undefined!
+```
+
+#### Using GoBackError in Steps
+
+To navigate back programmatically from a step:
+
+```typescript
+import { GoBackError } from '@microsoft/vscode-azext-utils';
+
+public async prompt(context: MyWizardContext): Promise<void> {
+  const result = await context.ui.showQuickPick(items, options);
+
+  if (result.isBackOption) {
+    // Clear step-specific selections before going back
+    context.selectedItem = undefined;
+    throw new GoBackError();
+  }
+
+  // Process selection...
+}
+```
+
 ### Tree View Architecture
 
 - Use proper data providers that implement `vscode.TreeDataProvider`.

.github/workflows/deploy-documentation-production.yml

@@ -0,0 +1,30 @@
+name: Deploy Documentation
+
+on:
+    push:
+        branches:
+            - main
+        paths:
+            - 'docs/**'
+    workflow_dispatch:
+
+permissions:
+    contents: write
+
+jobs:
+    deploy:
+        runs-on: ubuntu-latest
+        steps:
+            - name: 📥 Checkout Repository
+              uses: actions/checkout@v4
+              with:
+                  ref: main
+                  token: ${{ secrets.GITHUB_TOKEN }}
+
+            - name: 🚀 Deploy to GitHub Pages
+              uses: JamesIves/github-pages-deploy-action@v4
+              with:
+                  folder: docs/
+                  branch: gh-pages
+                  clean: true
+                  token: ${{ secrets.GITHUB_TOKEN }}

CHANGELOG.md

@@ -1,5 +1,19 @@
 # Change Log
 
+## 0.6.2
+
+### Fixes
+
+- **Azure Tenant Filtering in Service Discovery**: Resolved an issue where users could not deselect tenants when filtering from a large number of available tenants. This update improves the Azure account, tenant, and subscription management workflow. For more details on the enhanced workflow, see the [updated documentation](https://microsoft.github.io/vscode-documentdb/user-manual/managing-azure-discovery). [#391](https://github.com/microsoft/vscode-documentdb/issues/391), [#415](https://github.com/microsoft/vscode-documentdb/pull/415)
+- **Service Discovery Defaults**: The service discovery feature now starts with no pre-selected engines. Previously, the Azure Cosmos DB for MongoDB (RU) plugin was enabled by default, which has been corrected. [#390](https://github.com/microsoft/vscode-documentdb/issues/390), [#412](https://github.com/microsoft/vscode-documentdb/pull/412)
+- **Accessibility in Query Insights**: Fixed a responsive layout issue in the "Query Insights" tab where the 'AI response may be inaccurate' text would overlap with other UI elements on resize. [#376](https://github.com/microsoft/vscode-documentdb/issues/376), [#416](https://github.com/microsoft/vscode-documentdb/pull/416)
+
+### Improvements
+
+- **Dependency Upgrades**:
+  - Upgraded to React 19 and SlickGrid 9, enhancing UI performance and modernizing the webview components. This also includes updates to TypeScript, Webpack, and other build tools. [#406](https://github.com/microsoft/vscode-documentdb/issues/406), [#407](https://github.com/microsoft/vscode-documentdb/pull/407)
+  - Updated various other dependencies to improve security and performance. [#386](https://github.com/microsoft/vscode-documentdb/pull/386)
+
 ## 0.6.1
 
 ### New Features & Improvements

docs/index.md

@@ -64,7 +64,7 @@ The User Manual provides guidance on using DocumentDB for VS Code. It contains d
 
 Explore the history of updates and improvements to the DocumentDB for VS Code extension. Each release brings new features, enhancements, and fixes to improve your experience.
 
-- [0.6](./release-notes/0.6), [0.6.1](./release-notes/0.6#patch-release-v061)
+- [0.6](./release-notes/0.6), [0.6.1](./release-notes/0.6#patch-release-v061), [0.6.2](./release-notes/0.6#patch-release-v062)
 - [0.5](./release-notes/0.5), [0.5.1](./release-notes/0.5#patch-release-v051), [0.5.2](./release-notes/0.5#patch-release-v052)
 - [0.4](./release-notes/0.4), [0.4.1](./release-notes/0.4#patch-release-v041)
 - [0.3](./release-notes/0.3), [0.3.1](./release-notes/0.3#patch-release-v031)

docs/release-notes/0.6.md

@@ -78,15 +78,56 @@ This patch release introduces feedback optimization and fixes a broken link.
 
 ### What's Changed in v0.6.1
 
-#### **Feedback Optimization** ([#392](https://github.com/microsoft/vscode-documentdb/pull/392))
+#### 💠 **Feedback Optimization** ([#392](https://github.com/microsoft/vscode-documentdb/pull/392))
 
 Introduces privacy consent and feedback signal controls for the Query Insights feature, primarily to ensure compliance with organizational data protection requirements and user telemetry settings. It also disables survey functionality and refines the feedback dialog UI.
 
-#### **Privacy Policy Link Update** ([#388](https://github.com/microsoft/vscode-documentdb/pull/388))
+#### 💠 **Privacy Policy Link Update** ([#388](https://github.com/microsoft/vscode-documentdb/pull/388))
 
 Updated the outdated privacy policy link in the README to the current Microsoft privacy statement URL.
 
 ### Changelog
 
 See the full changelog entry for this release:
 ➡️ [CHANGELOG.md#061](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#061)
+
+---
+
+## Patch Release v0.6.2
+
+This patch release delivers important fixes for Azure tenant management, service discovery, and accessibility. It also includes a significant set of dependency upgrades to modernize the extension's underlying architecture.
+
+### What's Changed in v0.6.2
+
+#### 💠 **Improved Azure Tenant and Subscription Filtering in Service Discovery** ([#391](https://github.com/microsoft/vscode-documentdb/issues/391), [#415](https://github.com/microsoft/vscode-documentdb/pull/415))
+
+We've resolved a key issue that affected users managing numerous Azure tenants. Previously, when a user had access to a large number of tenants, and had selected all of them, the filtering wizard would fail to work correctly when attempting to deselect tenants, making it impossible to refine the resource view.
+
+This update introduces an improved filtering mechanism that ensures a reliable experience, even for users in enterprise environments. The wizard for managing accounts, tenants, and subscriptions is now more resilient, allowing you to precisely control which resources are displayed in the Service Discovery panel.
+
+For a complete guide on the enhanced workflow, please see our updated documentation on [Managing Azure Discovery](https://microsoft.github.io/vscode-documentdb/user-manual/managing-azure-discovery).
+
+#### 💠 **Corrected Service Discovery Default Settings** ([#390](https://github.com/microsoft/vscode-documentdb/issues/390), [#412](https://github.com/microsoft/vscode-documentdb/pull/412))
+
+To provide a cleaner initial experience, the Service Discovery feature no longer starts with any discovery engines enabled by default. In a previous version, the "Azure Cosmos DB for MongoDB (RU)" plugin was pre-selected by mistake, which could cause confusion.
+
+With this fix, you now have full control over which service discovery plugins are active from the start, for a more intentional and direct setup.
+
+#### 💠 **Accessibility Fix for Query Insights** ([#376](https://github.com/microsoft/vscode-documentdb/issues/376), [#416](https://github.com/microsoft/vscode-documentdb/pull/416))
+
+We've addressed an accessibility issue in the "Query Insights" tab where the "AI response may be inaccurate" warning text would overlap with other UI elements when the panel was resized. The layout has been updated to be fully responsive, ensuring all content remains readable and accessible regardless of panel size.
+
+#### 💠 **Modernized Architecture with Major Dependency Upgrades** ([#406](https://github.com/microsoft/vscode-documentdb/issues/406), [#407](https://github.com/microsoft/vscode-documentdb/pull/407), [#386](https://github.com/microsoft/vscode-documentdb/pull/386))
+
+This release includes a significant overhaul of our dev dependencies, bringing major performance and modernization improvements:
+
+- **Upgraded to React 19**: We've migrated our webview components to React 19, leveraging the latest features and performance enhancements from the React team.
+- **Upgraded to SlickGrid 9**: The data grids used to display collection data have been updated to SlickGrid 9. This major update improves rendering performance and aligns with modern JavaScript standards.
+- **Other Key Updates**: We've also updated TypeScript, Webpack, the MongoDB driver, and numerous other packages to enhance security, stability, and build performance.
+
+These upgrades ensure the extension remains fast, secure, and aligned with the latest web development best practices.
+
+### Changelog
+
+See the full changelog entry for this release:
+➡️ [CHANGELOG.md#062](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#062)