Prepare `0.7.0` release #464

tnaum-ms · 2026-01-23T12:32:07Z

No description provided.

Copilot

Pull request overview

Prepares the repository for the 0.7.0 release by bumping extension package versions and adding documentation/templates for generating release notes and changelog entries.

Changes:

Bump extension version from 0.6.3 to 0.7.0 in package.json and package-lock.json.
Add a “writing-release-notes” skill and supporting format/template docs under .github/skills/.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
package.json	Updates extension version to `0.7.0`.
package-lock.json	Aligns lockfile/package metadata version with `0.7.0`.
.github/skills/writing-release-notes/SKILL.md	Adds guidance for generating release notes and changelog entries.
.github/skills/writing-release-notes/RELEASE-NOTES-FORMAT.md	Adds a release-notes formatting reference and templates.
.github/skills/writing-release-notes/EXAMPLES-PATCH-RELEASE.md	Adds patch release examples and patterns.
.github/skills/writing-release-notes/EXAMPLES-MAJOR-RELEASE.md	Adds major/minor release examples and patterns.
.github/skills/writing-release-notes/CHANGELOG-FORMAT.md	Adds changelog entry formatting reference.

package.json

Copilot · 2026-01-23T12:34:41Z

.github/skills/writing-release-notes/RELEASE-NOTES-FORMAT.md

+## Changelog
+
+See the full changelog entry for this release:
+➡️ [CHANGELOG.md#XY0](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XY0)


The template uses a changelog anchor placeholder #XY0, but later in this document you define anchors as #XYZ where the version digits are concatenated (e.g., 0.6.0 → #060). To avoid confusion and broken links, consider using the same placeholder format everywhere (e.g., #XYZ with Z=0) and/or explicitly call out that XY0 is a placeholder that should become something like #070 for v0.7.0.

Suggested change

➡️ [CHANGELOG.md#XY0](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XY0)

➡️ [CHANGELOG.md#XYZ](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XYZ)

Copilot · 2026-01-23T12:34:41Z

.github/skills/writing-release-notes/EXAMPLES-MAJOR-RELEASE.md

+## Changelog
+
+See the full changelog entry for this release:
+➡️ [CHANGELOG.md#XY0](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XY0)


This template links to CHANGELOG.md#XY0, but the anchor scheme used in the repository’s CHANGELOG headings is numeric (e.g., ## 0.6.0 → #060). Using #XY0 here is likely to produce broken links if copied as-is; please align the placeholder with the numeric #XYZ convention described elsewhere.

Suggested change

➡️ [CHANGELOG.md#XY0](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XY0)

➡️ [CHANGELOG.md#XYZ](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XYZ)

Copilot · 2026-01-23T12:34:42Z

.github/skills/writing-release-notes/EXAMPLES-PATCH-RELEASE.md

+
+### What's Changed in v0.5.1
+
+#### **Improved Connection String Parsing** ([#314](https://github.com/microsoft/vscode-documentdb/issues/314), [#316](https://github.com/microsoft/vscode-documentdb/pull/316))


In Example 3, the item heading is missing the 💠 marker (#### 💠 **Title**) that the same document lists under “Item Formatting”. This makes the example inconsistent with the stated patch-release format; update the heading to match the pattern so readers can copy/paste reliably.

Suggested change

#### **Improved Connection String Parsing** ([#314](https://github.com/microsoft/vscode-documentdb/issues/314), [#316](https://github.com/microsoft/vscode-documentdb/pull/316))

#### 💠 **Improved Connection String Parsing** ([#314](https://github.com/microsoft/vscode-documentdb/issues/314), [#316](https://github.com/microsoft/vscode-documentdb/pull/316))

…rovements, and fixes

tnaum-ms · 2026-01-27T12:18:51Z

@copilot open a new pull request to apply changes based on the comments in this thread

Copilot · 2026-01-27T12:19:11Z

@tnaum-ms I've opened a new pull request, #466, to work on those changes. Once the pull request is ready, I'll request review from you.

…release notes docs Co-authored-by: tnaum-ms <171359267+tnaum-ms@users.noreply.github.com>

…umentation (#466)

…ontributions and various enhancements

Copilot

Pull request overview

Copilot reviewed 10 out of 12 changed files in this pull request and generated 6 comments.

Copilot · 2026-02-03T21:19:22Z

temp-list-of-changes.md

+PRs, when not provided in this input file, are linked from referenced issues, loook these up. look at descriptions of linked PRs for more context.
+
+hero features:
+
+# Lightweight Data Migration support
+
+https://github.com/microsoft/vscode-documentdb/issues/63
+
+This is a big annoucement, it helps with copying / moving data between systems, collections, databases. it's very powerful and very easy to use. it's like a copy and paste for files, but for collecgtions. it's smart, it works around conflicts, it deals with RU platforms and is able to adapt to throttle on writes.
+
+prompt: do note that the issue links to many sub issues, but the main feature issue number and link is #63 and this is enough to be referenced. same with the PR, this is the PR to link to https://github.com/microsoft/vscode-documentdb/pull/170
+describe the feature in release notes.
+
+the feature has a user-facing documentaiton descripiton, link to this file in the release notes, and use its content for more information about the feature for the release notes:
+vscode-documentdb/docs/user-manual/copy-and-paste.md
+
+# Folder Management for DocumentDB Connections View
+
+https://github.com/microsoft/vscode-documentdb/pull/426
+
+Users can now manage their connection list and organize connetions in folders, subfolders. introducing a huge improvement in comparison to the hisotorical / original flat list. this was an issue for many of our users who had more than a few connections.
+
+now, a user can gropu connections in fodlers / subfoders, and move them around as they see fit.
+
+# Accessibility
+
+A long list of accessibility related improvements. this is big as we're looking beyond functionality but also focus conitnously on accessibility:
+
+https://github.com/microsoft/vscode-documentdb/issues/385
+Keyboard focus not visible Immediately after opening "Edit Selected Document": A11y_DocumentDB for VS Code Extension_focusOrder
+
+https://github.com/microsoft/vscode-documentdb/issues/384
+ScreenReader does not announce search results count or "No Results Found" Information: A11y_DocumentDB for VS Code Extension_Screenreader
+
+https://github.com/microsoft/vscode-documentdb/issues/381
+NVDA is announcing the grouping label for like or dislike control:A11y_DocumentDB for VS Code Extension_View Query Insights_Screenreader
+
+https://github.com/microsoft/vscode-documentdb/issues/380
+NVDA is announcing 'Document' instead of announcing visual status message 'AI is analyzing :A11y_DocumentDB for VS Code Extension_View Query Insights_Screenreader
+
+https://github.com/microsoft/vscode-documentdb/issues/379
+No visual label provided for query field and programmatic name is misaligned with field purpose: A11y_DocumentDB for VS Code Extension_View Query Insights_Lable in Name
+
+https://github.com/microsoft/vscode-documentdb/issues/378
+Name is not give for Next, Previews and Close button:A11y_DocumentDB for VS Code Extension_View Query Insights_Devtool
+
+https://github.com/microsoft/vscode-documentdb/issues/377
+No accessible name provided for Skip and Limit Spin Buttons: A11y_DocumentDB for VS Code Extension_View Query Insights_Name
+
+https://github.com/microsoft/vscode-documentdb/issues/375
+All tool tip under "query insights" tab are not accessible with keyboard :A11y_DocumentDB for VS Code Extension_View Query Insights_Keyboard
+
+https://github.com/microsoft/vscode-documentdb/issues/374
+Visual label 'Refresh' is not part of accessibility name(Programmatic name) for "Refresh" button :A11y_DocumentDB for VS Code Extension_Add a New Document_Devtools
+
+---
+
+## Other improvements in this release / "no hero" features
+
+https://github.com/microsoft/vscode-documentdb/pull/170/changes/14dd6e67094221dd68fc5b3f7e86b45fda91059f
+<only a link to a commit>, no dedicated issue, no dediated PR:
+we added support to show an estimate count of documents for each collection in the collegtion view. this helps to quickly assess sizes of collections.
+
+https://github.com/microsoft/vscode-documentdb/issues/457
+Extension does not work with dark themes.
+
+https://github.com/microsoft/vscode-documentdb/issues/428
+Improved output formatting in AI generated responses of the "Query Insights" feature. We used unsupported markdown formatting characters resulting in malformed output in some scenarios. this has been fixed by restricting the formatting options available.
+
+https://github.com/microsoft/vscode-documentdb/pull/436
+added support for copy connection string with password
+
+when users copy connection details to clipboard, they can now choose whether they want to have the passowrd included as well, this was not available before, it wasn't possible ot copy a password.
+
+https://github.com/microsoft/vscode-documentdb/pull/434


This file reads like an internal scratchpad / prompt for generating release notes (e.g., “prompt: …”, raw links, and numerous typos). It’s likely not intended to ship in the repo as-is; consider removing it from the release PR (or moving the content to the PR description / an issue) to avoid permanent maintenance noise.

Suggested change

PRs, when not provided in this input file, are linked from referenced issues, loook these up. look at descriptions of linked PRs for more context.

hero features:

# Lightweight Data Migration support

https://github.com/microsoft/vscode-documentdb/issues/63

This is a big annoucement, it helps with copying / moving data between systems, collections, databases. it's very powerful and very easy to use. it's like a copy and paste for files, but for collecgtions. it's smart, it works around conflicts, it deals with RU platforms and is able to adapt to throttle on writes.

prompt: do note that the issue links to many sub issues, but the main feature issue number and link is #63 and this is enough to be referenced. same with the PR, this is the PR to link to https://github.com/microsoft/vscode-documentdb/pull/170

describe the feature in release notes.

the feature has a user-facing documentaiton descripiton, link to this file in the release notes, and use its content for more information about the feature for the release notes:

vscode-documentdb/docs/user-manual/copy-and-paste.md

# Folder Management for DocumentDB Connections View

https://github.com/microsoft/vscode-documentdb/pull/426

Users can now manage their connection list and organize connetions in folders, subfolders. introducing a huge improvement in comparison to the hisotorical / original flat list. this was an issue for many of our users who had more than a few connections.

now, a user can gropu connections in fodlers / subfoders, and move them around as they see fit.

# Accessibility

A long list of accessibility related improvements. this is big as we're looking beyond functionality but also focus conitnously on accessibility:

https://github.com/microsoft/vscode-documentdb/issues/385

Keyboard focus not visible Immediately after opening "Edit Selected Document": A11y_DocumentDB for VS Code Extension_focusOrder

https://github.com/microsoft/vscode-documentdb/issues/384

ScreenReader does not announce search results count or "No Results Found" Information: A11y_DocumentDB for VS Code Extension_Screenreader

https://github.com/microsoft/vscode-documentdb/issues/381

NVDA is announcing the grouping label for like or dislike control:A11y_DocumentDB for VS Code Extension_View Query Insights_Screenreader

https://github.com/microsoft/vscode-documentdb/issues/380

NVDA is announcing 'Document' instead of announcing visual status message 'AI is analyzing :A11y_DocumentDB for VS Code Extension_View Query Insights_Screenreader

https://github.com/microsoft/vscode-documentdb/issues/379

No visual label provided for query field and programmatic name is misaligned with field purpose: A11y_DocumentDB for VS Code Extension_View Query Insights_Lable in Name

https://github.com/microsoft/vscode-documentdb/issues/378

Name is not give for Next, Previews and Close button:A11y_DocumentDB for VS Code Extension_View Query Insights_Devtool

https://github.com/microsoft/vscode-documentdb/issues/377

No accessible name provided for Skip and Limit Spin Buttons: A11y_DocumentDB for VS Code Extension_View Query Insights_Name

https://github.com/microsoft/vscode-documentdb/issues/375

All tool tip under "query insights" tab are not accessible with keyboard :A11y_DocumentDB for VS Code Extension_View Query Insights_Keyboard

https://github.com/microsoft/vscode-documentdb/issues/374

Visual label 'Refresh' is not part of accessibility name(Programmatic name) for "Refresh" button :A11y_DocumentDB for VS Code Extension_Add a New Document_Devtools

---

## Other improvements in this release / "no hero" features

https://github.com/microsoft/vscode-documentdb/pull/170/changes/14dd6e67094221dd68fc5b3f7e86b45fda91059f

<only a link to a commit>, no dedicated issue, no dediated PR:

we added support to show an estimate count of documents for each collection in the collegtion view. this helps to quickly assess sizes of collections.

https://github.com/microsoft/vscode-documentdb/issues/457

Extension does not work with dark themes.

https://github.com/microsoft/vscode-documentdb/issues/428

Improved output formatting in AI generated responses of the "Query Insights" feature. We used unsupported markdown formatting characters resulting in malformed output in some scenarios. this has been fixed by restricting the formatting options available.

https://github.com/microsoft/vscode-documentdb/pull/436

added support for copy connection string with password

when users copy connection details to clipboard, they can now choose whether they want to have the passowrd included as well, this was not available before, it wasn't possible ot copy a password.

https://github.com/microsoft/vscode-documentdb/pull/434

# Release notes draft

## Hero features

### Lightweight data migration support

- Issue: [#63 – Lightweight Data Migration](https://github.com/microsoft/vscode-documentdb/issues/63)

- PR: [#170](https://github.com/microsoft/vscode-documentdb/pull/170)

- Documentation: [Copy and paste between databases and collections](https://github.com/microsoft/vscode-documentdb/blob/main/docs/user-manual/copy-and-paste.md)

This release introduces lightweight data migration, making it easy to copy or move data between systems, databases, and collections. The experience is similar to copying and pasting files, but for collections and documents. The feature is designed to handle conflicts intelligently and to respect request unit (RU) limits by adapting to throttling on writes.

### Folder management for DocumentDB Connections view

- PR: [#426 – Folder Management for Connections](https://github.com/microsoft/vscode-documentdb/pull/426)

Users can now organize their connections in folders and subfolders in the DocumentDB Connections view. This is a significant improvement over the previous flat list, especially for users who manage many connections. Connections can be grouped logically and moved between folders as needed.

### Accessibility improvements

A series of accessibility fixes improves both keyboard and screen reader experiences across the extension, particularly in Query Insights and document editing flows:

- [#385](https://github.com/microsoft/vscode-documentdb/issues/385) – Keyboard focus is now visible immediately after opening **Edit Selected Document**.

- [#384](https://github.com/microsoft/vscode-documentdb/issues/384) – Screen readers now announce search results count and “No Results Found” where appropriate.

- [#381](https://github.com/microsoft/vscode-documentdb/issues/381) – NVDA no longer announces an incorrect grouping label for like/dislike controls in Query Insights.

- [#380](https://github.com/microsoft/vscode-documentdb/issues/380) – NVDA now announces the correct visual status message “AI is analyzing” instead of a generic “Document” label.

- [#379](https://github.com/microsoft/vscode-documentdb/issues/379) – The query field now has a proper visual label and a programmatic name aligned with its purpose.

- [#378](https://github.com/microsoft/vscode-documentdb/issues/378) – Next, Previous, and Close buttons in Query Insights now have accessible names.

- [#377](https://github.com/microsoft/vscode-documentdb/issues/377) – Skip and Limit spin buttons now expose accessible names.

- [#375](https://github.com/microsoft/vscode-documentdb/issues/375) – Tooltips under the **Query Insights** tab are now accessible via keyboard.

- [#374](https://github.com/microsoft/vscode-documentdb/issues/374) – The **Refresh** button now includes the visual label in its accessibility name.

---

## Other improvements in this release

- Approximate document count per collection

- Commit (via PR #170): shows an estimated count of documents for each collection in the collections view, helping users quickly assess collection sizes.

- Dark theme compatibility

- [#457](https://github.com/microsoft/vscode-documentdb/issues/457) – Fixed issues that prevented the extension from working correctly with dark themes.

- Improved output formatting in Query Insights

- [#428](https://github.com/microsoft/vscode-documentdb/issues/428) – Improved formatting of AI-generated responses from **Query Insights** by avoiding unsupported markdown constructs that previously led to malformed output.

- Option to copy connection string with password

- [#436](https://github.com/microsoft/vscode-documentdb/pull/436) – Added an option to copy the connection string including the password when copying connection details to the clipboard. Previously, it was not possible to copy the password.

- Additional changes

- [#434](https://github.com/microsoft/vscode-documentdb/pull/434)

Copilot · 2026-02-03T21:19:22Z

CHANGELOG.md

+- **Lightweight Data Migration**: Introduces collection copy-and-paste feature for moving data between collections, databases, and servers. Supports four conflict resolution strategies (abort, skip, overwrite, generate new IDs), memory-efficient streaming with automatic throttle adaptation for RU platforms, real-time progress tracking, and configurable size warnings. Ideal for development workflows and smaller datasets. For production-scale migrations, dedicated migration services are recommended. [#63](https://github.com/microsoft/vscode-documentdb/issues/63), [#170](https://github.com/microsoft/vscode-documentdb/pull/170)
+- **Connection Folders**: Completely redesigns the Connections View to support hierarchical folder organization. Users can create folders and subfolders, move connections and folders using an intuitive wizard with validation, rename and delete items, and benefit from automatic sorting and visual hierarchy. Features boundary protection between emulator and non-emulator connections, and multi-item moving. [#426](https://github.com/microsoft/vscode-documentdb/pull/426)


The 0.7.0 changelog entries are much more verbose/marketing-oriented than the documented changelog format (1–2 factual sentences per bullet). Please tighten these bullets (and drop promotional phrasing) to align with .github/skills/writing-release-notes/CHANGELOG-FORMAT.md rules (e.g., lines 45–49).

Copilot · 2026-02-03T21:19:22Z

CHANGELOG.md

+### Community Contributions
+
+- **Alphabetical Collection Sorting**: Collections within MongoDB databases are now displayed in alphabetical order for better readability and consistency. Contributed by [@VanitasBlade](https://github.com/VanitasBlade), fixing issue [#456](https://github.com/microsoft/vscode-documentdb/issues/456) reported by [@majelbstoat](https://github.com/majelbstoat). [#465](https://github.com/microsoft/vscode-documentdb/pull/465)


The changelog format reference doesn’t list a “Community Contributions” category (it specifies New Features/Improvements/Fixes/Security). Consider folding this item into the appropriate existing category (and optionally mention the contributor in the bullet) to keep CHANGELOG.md consistent with .github/skills/writing-release-notes/CHANGELOG-FORMAT.md:27-35.

Copilot · 2026-02-03T21:19:23Z

CHANGELOG.md

+### Fixes
+
+- **Dark Theme Support**: Resolves UI rendering issues affecting users of dark themes like Nord, where text in certain controls appeared dark-on-dark and invisible. All UI elements now properly respect theme colors for excellent visibility in both light and dark modes. [#457](https://github.com/microsoft/vscode-documentdb/issues/457)
+- **AI Response Formatting**: Corrects markdown formatting in AI-generated responses from the Query Insights feature by restricting formatting options to prevent malformed output. [#428](https://github.com/microsoft/vscode-documentdb/issues/428)
+- **Security Dependency Updates**: Updates `qs` and `express` dependencies to address security vulnerabilities and maintain high security standards. [#434](https://github.com/microsoft/vscode-documentdb/pull/434)
+- **Query Parsing Error Handling**: Fixed invalid JSON query inputs no longer being silently replaced with empty objects. Parse failures now surface clear error messages with helpful JSON examples, improving user feedback. Reported by [@majelbstoat](https://github.com/majelbstoat) in [#458](https://github.com/microsoft/vscode-documentdb/issues/458). [#471](https://github.com/microsoft/vscode-documentdb/pull/471)


“Security Dependency Updates” is currently under “### Fixes”, but the changelog format reference calls out a dedicated “### Security” section for security-related updates. Consider moving this bullet under a new “### Security” heading for 0.7.0 to match the documented categories.

Copilot · 2026-02-03T21:19:23Z

docs/release-notes/0.7.md

+Invalid JSON in query fields was being silently replaced with empty objects, making debugging difficult. Parse failures now show clear error messages with helpful JSON syntax examples.
+
+**Reported by [@majelbstoat](https://github.com/majelbstoat)**.
+
+### 3️⃣ Keyboard Paste Restored ([#435](https://github.com/microsoft/vscode-documentdb/issues/435), [#470](https://github.com/microsoft/vscode-documentdb/pull/470))
+
+Keyboard paste shortcuts (`Ctrl+V` / `Cmd+V`) stopped working in the Query Editor and Document View due to a Monaco Editor regression. Downgrading to Monaco 0.52.2 restored this functionality.


These two community contribution items (“Invalid Query Parsing Fixed” and “Keyboard Paste Restored”) are repeated again in the “Key Fixes” section below. Consider referencing each fix in only one place (or cross-linking) to avoid duplicated release note content.

Suggested change

Invalid JSON in query fields was being silently replaced with empty objects, making debugging difficult. Parse failures now show clear error messages with helpful JSON syntax examples.

**Reported by [@majelbstoat](https://github.com/majelbstoat)**.

### 3️⃣ Keyboard Paste Restored ([#435](https://github.com/microsoft/vscode-documentdb/issues/435), [#470](https://github.com/microsoft/vscode-documentdb/pull/470))

Keyboard paste shortcuts (`Ctrl+V` / `Cmd+V`) stopped working in the Query Editor and Document View due to a Monaco Editor regression. Downgrading to Monaco 0.52.2 restored this functionality.

This fix improves how invalid JSON in query fields is handled; full technical details are documented in the [Key Fixes](#key-fixes) section.

**Reported by [@majelbstoat](https://github.com/majelbstoat)**.

### 3️⃣ Keyboard Paste Restored ([#435](https://github.com/microsoft/vscode-documentdb/issues/435), [#470](https://github.com/microsoft/vscode-documentdb/pull/470))

This restores keyboard paste shortcuts (`Ctrl+V` / `Cmd+V`) in the Query Editor and Document View; see [Key Fixes](#key-fixes) for more details.

Copilot · 2026-02-03T21:19:23Z

docs/release-notes/0.7.md

+
+### Azure Resources View Connectivity ([#480](https://github.com/microsoft/vscode-documentdb/pull/480))
+
+Resolved connection failures when expanding Azure DocumentDB clusters in the Azure Resources view. Previously, undefined resource group metadata caused cryptic API errors. The extension now correctly extracts resource group information from resource IDs, ensuring reliable connectivity to vCore and Azure Cosmos DB for MongoDB (RU)clusters.


Typo: missing space in “(RU)clusters”.

Suggested change

Resolved connection failures when expanding Azure DocumentDB clusters in the Azure Resources view. Previously, undefined resource group metadata caused cryptic API errors. The extension now correctly extracts resource group information from resource IDs, ensuring reliable connectivity to vCore and Azure Cosmos DB for MongoDB (RU)clusters.

Resolved connection failures when expanding Azure DocumentDB clusters in the Azure Resources view. Previously, undefined resource group metadata caused cryptic API errors. The extension now correctly extracts resource group information from resource IDs, ensuring reliable connectivity to vCore and Azure Cosmos DB for MongoDB (RU) clusters.

tnaum-ms added 2 commits January 20, 2026 21:10

feat: new skill for changelog, release notes, and patch release notes

329d8dd

version bump to 0/7.0

54aad5b

tnaum-ms requested a review from a team as a code owner January 23, 2026 12:32

Copilot AI review requested due to automatic review settings January 23, 2026 12:32

Merge branch 'next' into dev/tnaum/prepare-0.7.0-release

9ca684b

Copilot started reviewing on behalf of tnaum-ms January 23, 2026 12:32 View session

Copilot AI reviewed Jan 23, 2026

View reviewed changes

chore: update release notes for version 0.7, adding new features, imp…

a2ef8b5

…rovements, and fixes

Initial plan

c29c95a

Copilot AI mentioned this pull request Jan 27, 2026

Fix changelog anchor placeholders and formatting in release notes documentation #466

Merged

Copilot AI and others added 2 commits January 27, 2026 12:20

fix: correct changelog anchor placeholders and add missing marker in …

539bf8f

…release notes docs Co-authored-by: tnaum-ms <171359267+tnaum-ms@users.noreply.github.com>

Fix changelog anchor placeholders and formatting in release notes doc…

b6b0663

…umentation (#466)

tnaum-ms added this to the 0.7.0 - January 2025 milestone Jan 29, 2026

tnaum-ms added 2 commits February 3, 2026 18:12

Merge branch 'next' into dev/tnaum/prepare-0.7.0-release

adf2167

chore: update release notes for version 0.7, highlighting community c…

8d4d1a0

…ontributions and various enhancements

tnaum-ms requested a review from Copilot February 3, 2026 21:15

Copilot started reviewing on behalf of tnaum-ms February 3, 2026 21:15 View session

Copilot AI reviewed Feb 3, 2026

View reviewed changes

khelanmodi self-requested a review February 3, 2026 21:25

khelanmodi approved these changes Feb 3, 2026

View reviewed changes

	➡️ [CHANGELOG.md#XY0](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XY0)
	➡️ [CHANGELOG.md#XYZ](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#XYZ)


		### What's Changed in v0.5.1

		#### Improved Connection String Parsing ([#314](https://github.com/microsoft/vscode-documentdb/issues/314), [#316](https://github.com/microsoft/vscode-documentdb/pull/316))

	#### Improved Connection String Parsing ([#314](https://github.com/microsoft/vscode-documentdb/issues/314), [#316](https://github.com/microsoft/vscode-documentdb/pull/316))
	#### 💠 Improved Connection String Parsing ([#314](https://github.com/microsoft/vscode-documentdb/issues/314), [#316](https://github.com/microsoft/vscode-documentdb/pull/316))

		- Lightweight Data Migration: Introduces collection copy-and-paste feature for moving data between collections, databases, and servers. Supports four conflict resolution strategies (abort, skip, overwrite, generate new IDs), memory-efficient streaming with automatic throttle adaptation for RU platforms, real-time progress tracking, and configurable size warnings. Ideal for development workflows and smaller datasets. For production-scale migrations, dedicated migration services are recommended. [#63](https://github.com/microsoft/vscode-documentdb/issues/63), [#170](https://github.com/microsoft/vscode-documentdb/pull/170)
		- Connection Folders: Completely redesigns the Connections View to support hierarchical folder organization. Users can create folders and subfolders, move connections and folders using an intuitive wizard with validation, rename and delete items, and benefit from automatic sorting and visual hierarchy. Features boundary protection between emulator and non-emulator connections, and multi-item moving. [#426](https://github.com/microsoft/vscode-documentdb/pull/426)

		### Community Contributions

		- Alphabetical Collection Sorting: Collections within MongoDB databases are now displayed in alphabetical order for better readability and consistency. Contributed by [@VanitasBlade](https://github.com/VanitasBlade), fixing issue [#456](https://github.com/microsoft/vscode-documentdb/issues/456) reported by [@majelbstoat](https://github.com/majelbstoat). [#465](https://github.com/microsoft/vscode-documentdb/pull/465)


		### Azure Resources View Connectivity ([#480](https://github.com/microsoft/vscode-documentdb/pull/480))

		Resolved connection failures when expanding Azure DocumentDB clusters in the Azure Resources view. Previously, undefined resource group metadata caused cryptic API errors. The extension now correctly extracts resource group information from resource IDs, ensuring reliable connectivity to vCore and Azure Cosmos DB for MongoDB (RU)clusters.

Prepare 0.7.0 release #464

Are you sure you want to change the base?

Prepare 0.7.0 release #464

Uh oh!

Conversation

tnaum-ms commented Jan 23, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

tnaum-ms commented Jan 27, 2026

Uh oh!

Copilot AI commented Jan 27, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Prepare `0.7.0` release #464

Prepare `0.7.0` release #464