Changelog updates for 1.45.0 release - #22676
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the repository and extension changelogs to include the release notes section for the upcoming 1.45.0 release, aligning with the release-tracking issue.
Changes:
- Added a new Version 1.45.0 section (release date/status + “What’s new” bullets) to the root changelog.
- Mirrored the same Version 1.45.0 section into
extensions/mssql/CHANGELOG.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CHANGELOG.md | Adds the 1.45.0 release section and highlights for the overall repo changelog. |
| extensions/mssql/CHANGELOG.md | Adds the same 1.45.0 release section for the extension-specific changelog. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
PR Changes
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #22676 +/- ##
==========================================
- Coverage 88.74% 87.70% -1.05%
==========================================
Files 340 340
Lines 119800 119800
Branches 552 552
==========================================
- Hits 106317 105071 -1246
- Misses 13483 14729 +1246
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
Suppressed comments (3)
extensions/sql-database-projects/CHANGELOG.md:12
- The 1.7.0 bullets have inconsistent punctuation and one sentence reads ungrammatically ("Added support for Move to Schema now automatically moves..."). Consider adding a period for consistency and rephrasing the Move to Schema bullet for clarity.
- Added support for using **Move to Schema** on sequences and DML triggers
- Added a **Restore Packages** command to the SQL project context menu for restoring the project's NuGet packages.
- Added support for **Move to Schema** now automatically moves the `.sql` file to the target schema folder.
extensions/mssql/CHANGELOG.md:14
- The changelog entry says "Restore command" but the UI command appears to be named "Restore Packages". Using the exact command name in the changelog avoids confusion for users searching settings/commands.
- Added a Restore command to the SQL Database Projects tree and support for custom code analysis rules from NuGet analyzer packages.
CHANGELOG.md:14
- The changelog entry says "Restore command" but the UI command appears to be named "Restore Packages". Using the exact command name in the changelog avoids confusion for users searching settings/commands.
- Added a Restore command to the SQL Database Projects tree and support for custom code analysis rules from NuGet analyzer packages.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 8 out of 8 changed files in this pull request and generated no new comments.
Suppressed comments (2)
extensions/mssql/src/webviews/common/locConstants.ts:447
- These
l10n.t("…")message strings are also localization keys; changing them from "Shortcuts Configuration (Preview)" to "Shortcuts Configuration" requires updating the localized XLF/LCL assets for other locales, otherwise those locales will lose the translation and fall back to English. The repo still contains the old key in multiple locale files (e.g.localization/xliff/vscode-mssql.de.xlf:9301,localization/LCL/de/vscode-mssql.xlf.lcl:1590).
public get shortcutsConfiguration() {
return {
title: l10n.t("Shortcuts Configuration"),
pageAriaLabel: l10n.t("Shortcuts configuration page"),
extensions/mssql/src/webviews/common/locConstants.ts:2554
- Changing this localized string from "Create an Azure SQL Database (Preview)" to "Create an Azure SQL Database" updates the localization key; make sure the locale XLF/LCL files are updated as well, otherwise non-English locales will miss this translation. The old key is still present in multiple locale files (e.g.
localization/xliff/vscode-mssql.fr.xlf:2611,localization/LCL/fr/vscode-mssql.xlf.lcl:17970).
return {
loadingAzureSqlDatabase: l10n.t("Loading Azure SQL Database..."),
azureSqlDatabaseHeader: l10n.t("Create an Azure SQL Database"),
azureSqlDatabaseDescription: l10n.t(
|
|
||
| ### What's new in 1.45.0 | ||
|
|
||
| - Released Azure SQL and Fabric provisioning as generally available (GA), with favorite resources and post-deployment actions to connect to the database, download deployment scripts, and discover next steps. |
There was a problem hiding this comment.
Fabric provisioning was already GA, only Azure SQL is newly GA. Use the same descriptive text as when it went to public preview; don't mention favorite resources but you can keep mention of post-deployment actions (ARM template, Bicep, and Terraform)
There was a problem hiding this comment.
Updated in 8d0dc0e: the bullet now covers only Azure SQL Database provisioning going GA, reuses the public preview description, drops favorite resources, and keeps the post-deployment actions (ARM template, Bicep, and Terraform).
|
|
||
| - Released Azure SQL and Fabric provisioning as generally available (GA), with favorite resources and post-deployment actions to connect to the database, download deployment scripts, and discover next steps. | ||
| - Released Shortcuts Configuration as generally available (GA), allowing you to create and manage keyboard shortcuts for Quick Queries, the Query Editor, and the Results Grid. | ||
| - Introduced a new SQL formatter (Preview), enabled by default with `mssql.format.enablePreviewFormatter` and an option to temporarily use the existing formatter. |
There was a problem hiding this comment.
Describe what the formatter brings, don't mention the option to use the old one
There was a problem hiding this comment.
Updated in cdad9d9: the formatter bullet now describes the more consistent T-SQL formatting and its options (keyword casing, clause and column alignment, indentation, comment preservation) without mentioning falling back to the existing formatter.
| - Released Azure SQL and Fabric provisioning as generally available (GA), with favorite resources and post-deployment actions to connect to the database, download deployment scripts, and discover next steps. | ||
| - Released Shortcuts Configuration as generally available (GA), allowing you to create and manage keyboard shortcuts for Quick Queries, the Query Editor, and the Results Grid. | ||
| - Introduced a new SQL formatter (Preview), enabled by default with `mssql.format.enablePreviewFormatter` and an option to temporarily use the existing formatter. | ||
| - Added a new React Flow execution plan renderer (Preview). Enable it with `mssql.preview.betaExecutionPlan` in settings. |
There was a problem hiding this comment.
Leave the implementation details out, just say it's a new one with better performance
There was a problem hiding this comment.
Updated in cdad9d9: it now reads as a new execution plan viewer (Preview) with improved performance, plus the setting to enable it.
|
Copilot address the comments I've left on this PR. Keep the edited changelog.md files in-sync, and update the root and mssql README files to include the new preview flags. |
Co-authored-by: Benjin <1609827+Benjin@users.noreply.github.com>
Done in cdad9d9. Root and Note: my earlier reply on the provisioning thread cited the wrong hash — the correct commit is cdad9d9. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 10 changed files in this pull request and generated no new comments.
Suppressed comments (4)
README.md:171
- The comments for the formatter settings imply these options always apply, but most of them are only used when the preview formatter is disabled (per the setting descriptions). This snippet should label the legacy-only settings to avoid misleading users (especially since the preview formatter defaults to enabled).
"mssql.format.enablePreviewFormatter": true, // (Preview) Use the new SQL formatter with additional formatting options
"mssql.format.alignColumnDefinitionsInColumns": false, // Align column definitions in CREATE TABLE statements
"mssql.format.datatypeCasing": "none", // Datatype casing: "none" | "uppercase" | "lowercase"
"mssql.format.keywordCasing": "none", // SQL keyword casing: "none" | "uppercase" | "lowercase"
"mssql.format.placeCommasBeforeNextStatement": false, // Place commas before next item (procedural style)
extensions/mssql/README.md:171
- The comments for the formatter settings imply these options always apply, but most of them are only used when the preview formatter is disabled (per the setting descriptions). This snippet should label the legacy-only settings to avoid misleading users (especially since the preview formatter defaults to enabled).
"mssql.format.enablePreviewFormatter": true, // (Preview) Use the new SQL formatter with additional formatting options
"mssql.format.alignColumnDefinitionsInColumns": false, // Align column definitions in CREATE TABLE statements
"mssql.format.datatypeCasing": "none", // Datatype casing: "none" | "uppercase" | "lowercase"
"mssql.format.keywordCasing": "none", // SQL keyword casing: "none" | "uppercase" | "lowercase"
"mssql.format.placeCommasBeforeNextStatement": false, // Place commas before next item (procedural style)
README.md:48
- The GA features table lists “Fabric integration” and “Query Profiler” twice. This makes the feature list harder to scan and looks like an accidental duplication; consider removing the duplicate rows (keeping only one entry for each capability).
| [Data-tier Application (DACPAC and BACPAC)](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-data-tier-application) | Deploy, extract, import, and export DACPAC and BACPAC files |
| [Fabric integration](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-fabric-integration) | Browse Fabric workspaces and provision SQL databases |
| [SQL Database Projects](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code) | Build, publish with the visual Publish Dialog, and analyze SQL projects with Code Analysis |
| [Query Profiler](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-query-profiler) | Real-time database activity monitoring with Extended Events |
extensions/mssql/README.md:48
- The GA features table lists “Fabric integration” and “Query Profiler” twice. This makes the feature list harder to scan and looks like an accidental duplication; consider removing the duplicate rows (keeping only one entry for each capability).
| [Data-tier Application (DACPAC and BACPAC)](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-data-tier-application) | Deploy, extract, import, and export DACPAC and BACPAC files |
| [Fabric integration](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-fabric-integration) | Browse Fabric workspaces and provision SQL databases |
| [SQL Database Projects](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code) | Build, publish with the visual Publish Dialog, and analyze SQL projects with Code Analysis |
| [Query Profiler](https://learn.microsoft.com/sql/tools/visual-studio-code-extensions/mssql/mssql-query-profiler) | Real-time database activity monitoring with Extended Events |
Description
Addresses #22675
Please review the proposed changelog update and make any necessary changes before merging.
Release readiness checks
CHANGELOG.md,extensions/mssql/CHANGELOG.md, andextensions/mssql/src/configurations/changelog.ts.Previewlabels andisPreviewflags have been removed from features moving to GA.Preview.🤖 This PR was automatically created by the Release Manager agent to propose an update to the changelog for the upcoming 1.45.0 release.
Code Changes Checklist
npm run test)Reviewers: Please read our reviewer guidelines