From f477d15bbb2a19518376b2c142f433473c05c135 Mon Sep 17 00:00:00 2001 From: Alex Weininger Date: Wed, 22 Jan 2025 16:54:04 -0500 Subject: [PATCH] Prep for v0.13.0 release (#1022) --- CHANGELOG.md | 8 ++++++++ package-lock.json | 4 ++-- package.json | 2 +- 3 files changed, 11 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index da313edd..bc81de50 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,6 +1,14 @@ # Change Log All notable changes to the "ms-vscode.azure-account" extension will be documented in this file. +## [0.13.0] - 2025-01-22 + +The Azure Account extension is deprecated (January 2025). The extension will still be available on the marketplace to support extensions that haven't moved to the built-in Microsoft authentication extension. Please see the [Azure Resources README](https://github.com/microsoft/vscode-azureresourcegroups?tab=readme-ov-file#move-to-built-in-vs-code-authentication) for how to manage Azure accounts in VS Code using the new built-in Microsoft authentication extension. + +To avoid confusion among users, we've hidden the status bar item that shows the signed-in account email address. The extension will no longer show the email address in the status bar by default. If you want to show the status bar item, you can enable it by enabling the `azure.azure-account.showStatusBar` setting. + +If you own an Azure extension that relies on Azure Account, or are creating a new extension that needs authentication to Azure, please see the [deprecation announcement](https://github.com/microsoft/vscode-azure-account/issues/964) for guidance. + ## [0.12.0] - 2024-05-14 In preparation of the [Azure Account extension being deprecated](https://github.com/microsoft/vscode-azure-account/issues/964) at the end of the year, we've moved the Azure Cloud Shell feature to the [Azure Resources extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureresourcegroups). Apart from moving codebases, the feature is the same from a users perspective. Authentication for the Cloud Shell feature is now handled by the VS Code built-in Microsoft authentication provider, which means you may have to login upon first use of the migrated feature. diff --git a/package-lock.json b/package-lock.json index 7debf1da..e4c079d4 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "azure-account", - "version": "0.12.0", + "version": "0.13.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "azure-account", - "version": "0.12.0", + "version": "0.13.0", "license": "SEE LICENSE IN LICENSE.md", "dependencies": { "@azure/arm-resources": "^4.2.2", diff --git a/package.json b/package.json index 4d09c847..2a9ff314 100644 --- a/package.json +++ b/package.json @@ -15,7 +15,7 @@ "color": "#0072c6", "theme": "dark" }, - "version": "0.12.0", + "version": "0.13.0", "aiKey": "0c6ae279ed8443289764825290e4f9e2-1a736e7c-1324-4338-be46-fc2a58ae4d14-7255", "publisher": "ms-vscode", "engines": {