diff --git a/CHANGELOG.md b/CHANGELOG.md
index caaf9dd5..da313edd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,6 +1,20 @@
 # Change Log
 All notable changes to the "ms-vscode.azure-account" extension will be documented in this file.
 
+## [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.
+
+Additionally, we've fixed two longstanding Azure Cloud Shell bugs that caused issues launching the feature on Linux and macOS: [#719](https://github.com/microsoft/vscode-azure-account/issues/719) and [#959](https://github.com/microsoft/vscode-azure-account/issues/959).
+
+### Changed
+* [[958]](https://github.com/microsoft/vscode-azure-account/pull/958) Depend on Azure Resources extension for the Azure Cloud Shell feature 
+
+### Fixed
+
+* [[855]](https://github.com/microsoft/vscode-azureresourcegroups/pull/855) Stop using `--ms-enable-electron-run-as-node` flag to fix launching Cloud Shell on macOS
+* [[854]](https://github.com/microsoft/vscode-azureresourcegroups/pull/854) Use `process.execPath` instead of `process.argv0` to fix launching Cloud Shell on Linux
+
 ## [0.11.7] - 2024-04-30
 
 ### Added
diff --git a/README.md b/README.md
index 87dad415..076739b1 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,8 @@ Sign out of Azure using the `Azure: Sign Out` command.
 
 ## Azure Cloud Shell
 
+> Note: The Azure Cloud Shell feature has moved 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.
+
 Azure Cloud Shell instances can be started via the terminal view in VS Code. To begin, click the
 dropdown arrow in the terminal view and select from either `Azure Cloud Shell (Bash)` or
 `Azure Cloud Shell (PowerShell)`.
diff --git a/package-lock.json b/package-lock.json
index 5fdbf9dc..6aa418e3 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
     "name": "azure-account",
-    "version": "0.11.7",
+    "version": "0.12.0",
     "lockfileVersion": 2,
     "requires": true,
     "packages": {
         "": {
             "name": "azure-account",
-            "version": "0.11.7",
+            "version": "0.12.0",
             "license": "SEE LICENSE IN LICENSE.md",
             "dependencies": {
                 "@azure/arm-resources": "^4.2.2",
diff --git a/package.json b/package.json
index e6972ecc..cc0bc2cb 100644
--- a/package.json
+++ b/package.json
@@ -15,7 +15,7 @@
         "color": "#0072c6",
         "theme": "dark"
     },
-    "version": "0.11.7",
+    "version": "0.12.0",
     "aiKey": "0c6ae279ed8443289764825290e4f9e2-1a736e7c-1324-4338-be46-fc2a58ae4d14-7255",
     "publisher": "ms-vscode",
     "engines": {