Releases: forcedotcom/salesforcedx-vscode
Release v63.11.0
63.11.0 - April 30, 2025
Fixed
salesforcedx-vscode-core
-
The following commands are now only visible and executable for files and folders within the paths specified in the
packageDirectoriesarray ofsfdx-project.json: -
SDFX:Deploy to Org -
SFDX:Retrieve from Org -
SFDX:Diff Against Org -
SFDX:Delete from Org -
SFDX:Create Manifest
These commands no longer appear in the Explorer View context menu, Editor View context menu, or Command Palette for resources outside the defined packageDirectories, including anything outside the force-app directory. Previously, attempting to run these commands on files or folders outside the configured package directories resulted in errors during deployment or retrieval. (PR #6224)
63.10.0 - April 23, 2025
Added
salesforcedx-vscode-core
-
We've now deprecated the
SFDX: Create a Lightning Web Component Testcommand. It's no longer available from the command palette. (PR #6225) -
We bumped SDR and some libraries to catch up with the latest. This update fixed an issue with deploying and retrieving
DigitalExperienceBundlemetadata. (PR #6223) -
We enhanced telemetry for Agentforce for Developers by making changes under the hood. (PR #6171)
Fixed
salesforcedx-vscode-apex
- We updated the text for the Java home setting to reflect currently supported versions. (PR #6228, PR #6229)
63.9.2 - April 17, 2025
Fixed
salesforcedx-vscode-core
- We fixed the import in the Lightning web components (LWC) test template so that newly created LWC tests won't contain any errors in the Problems Tab. (PR #661, PR #662, PR #6207, PR #6209)
salesforcedx-vscode-apex
- We fixed an issue where an Apex variable with a number in the middle of its name was previously treated as two separate variables. (PR #6184)
- We fixed an issue where the
SFDX: Restart Apex Language Servercommand wasn't always visible. Now it's always visible. (PR #6187) - We improved the UX for restarting the Apex Language Server by making the notification in the Apex menu seamlessly guide users to the new
SFDX: Restart Apex Language Servercommand in the Command Palette. This ensures a smoother, and more intuitive workflow. (PR #6194) - We now support any Java version that is 11 or higher. (PR #6201)
- We made some changes under the hood. (PR #6187, PR #6195, PR #6189)
salesforcedx-apex-replay-debugger
- We made some changes under the hood. (PR #6206)
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
-...
Release v63.10.0
63.10.0 - April 23, 2025
Added
salesforcedx-vscode-core
-
We've now deprecated the
SFDX: Create a Lightning Web Component Testcommand. It's no longer available from the command palette. (PR #6225) -
We bumped SDR and some libraries to catch up with the latest. This update fixed an issue with deploying and retrieving
DigitalExperienceBundlemetadata. (PR #6223) -
We enhanced telemetry for Agentforce for Developers by making changes under the hood. (PR #6171)
Fixed
salesforcedx-vscode-apex
- We updated the text for the Java home setting to reflect currently supported versions. (PR #6228, PR #6229)
63.9.2 - April 17, 2025
Fixed
salesforcedx-vscode-core
- We fixed the import in the Lightning web components (LWC) test template so that newly created LWC tests won't contain any errors in the Problems Tab. (PR #661, PR #662, PR #6207, PR #6209)
salesforcedx-vscode-apex
- We fixed an issue where an Apex variable with a number in the middle of its name was previously treated as two separate variables. (PR #6184)
- We fixed an issue where the
SFDX: Restart Apex Language Servercommand wasn't always visible. Now it's always visible. (PR #6187) - We improved the UX for restarting the Apex Language Server by making the notification in the Apex menu seamlessly guide users to the new
SFDX: Restart Apex Language Servercommand in the Command Palette. This ensures a smoother, and more intuitive workflow. (PR #6194) - We now support any Java version that is 11 or higher. (PR #6201)
- We made some changes under the hood. (PR #6187, PR #6195, PR #6189)
salesforcedx-apex-replay-debugger
- We made some changes under the hood. (PR #6206)
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. ([PR #5939](https://github.com/forcedotcom/salesforcedx-vscode/pull/...
Release v63.9.2
63.9.2 - April 17, 2025
Fixed
salesforcedx-vscode-core
- We fixed the import in the Lightning web components (LWC) test template so that newly created LWC tests won't contain any errors in the Problems Tab. (PR #661, PR #662, PR #6207, PR #6209)
salesforcedx-vscode-apex
- We fixed an issue where an Apex variable with a number in the middle of its name was previously treated as two separate variables. (PR #6184)
- We fixed an issue where the
SFDX: Restart Apex Language Servercommand wasn't always visible. Now it's always visible. (PR #6187) - We improved the UX for restarting the Apex Language Server by making the notification in the Apex menu seamlessly guide users to the new
SFDX: Restart Apex Language Servercommand in the Command Palette. This ensures a smoother, and more intuitive workflow. (PR #6194) - We now support any Java version that is 11 or higher. (PR #6201)
- We made some changes under the hood. (PR #6187, PR #6195, PR #6189)
salesforcedx-apex-replay-debugger
- We made some changes under the hood. (PR #6206)
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. ([PR #5900](https://github.com/forcedotcom/s...
Release v63.9.1
63.9.1 - April 17, 2025
Fixed
salesforcedx-vscode-core
- We fixed the import in the Lightning web components (LWC) test template so that newly created LWC tests won't contain any errors in the Problems Tab. (PR #6207)
salesforcedx-vscode-apex
- We fixed an issue where an Apex variable with a number in the middle of its name was previously treated as two separate variables. (PR #6184)
- We fixed an issue where the
SFDX: Restart Apex Language Servercommand wasn't always visible. Now it's always visible. (PR #6187) - We improved the UX for restarting the Apex Language Server by making the notification in the Apex menu seamlessly guide users to the new
SFDX: Restart Apex Language Servercommand in the Command Palette. This ensures a smoother, and more intuitive workflow. (PR #6194) - We now support any Java version that is 11 or higher. (PR #6201)
- We made some changes under the hood. (PR #6187, PR #6195, PR #6189)
salesforcedx-apex-replay-debugger
- We made some changes under the hood. (PR #6206)
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We ad...
Release v63.8.2
63.8.2 - April 11, 2025
Fixed
salesforcedx-vscode-apex
- We fixed an issue where an Apex variable with a number in the middle of its name was previously treated as two separate variables. (PR #6184)
- We fixed an issue where the
SFDX: Restart Apex Language Servercommand wasn't always visible. Now it's always visible. (PR #6187) - We improved the UX for restarting the Apex Language Server by making the notification in the Apex menu seamlessly guide users to the new
SFDX: Restart Apex Language Servercommand in the Command Palette. This ensures a smoother, and more intuitive workflow.(PR #6194) - We made some changes under the hood. (PR #6187, PR #6195, PR #6189)
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We added telemetry to the Apex Language Server, so you can track all errors and exceptions. To see them, select the "Apex Language Server" dropdown in the Output tab. Want to enable or disable telemetry? Use the
Salesforcedx-vscode-core › Telemetrysetting. (PR #5897)
62.0.0 - October 9, 2024
Fixed
salesforcedx-vscode-apex
- We updated the Java Home Setting description to include Java 21. (PR #5878)
- We ...
Release v63.8.0
63.8.0 - April 9, 2025
Fixed
salesforcedx-vscode-apex
- We fixed an issue where an Apex variable with a number in the middle of its name was previously treated as two separate variables. (PR #6184)
- We fixed an issue where the
SFDX: Restart Apex Language Servercommand wasn't always visible. Now it's always visible. (PR #6187) - We made some changes under the hood. (PR #6187)
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We added telemetry to the Apex Language Server, so you can track all errors and exceptions. To see them, select the "Apex Language Server" dropdown in the Output tab. Want to enable or disable telemetry? Use the
Salesforcedx-vscode-core › Telemetrysetting. (PR #5897)
62.0.0 - October 9, 2024
Fixed
salesforcedx-vscode-apex
- We updated the Java Home Setting description to include Java 21. (PR #5878)
- We updated the Apex Language Server to support the latest features and improvements of the language. When you activate the new of the Apex extension for the first time, you could experience some lag while your workspace is upgraded to 252 Apex artifacts and your project is fully indexed. (PR #5887)
salesforcedx-vscode-core
- We fixed some labels in the Org Browser. ([PR #5714](https://github.com/forcedotcom/sales...
Release v63.7.0
63.7.0 - April 2, 2025
Added
salesforcedx-vscode-core
salesforcedx-vscode-apex
- We updated the Org Browser to include more lightning component types. (PR #6174)
- Use the new
SFDX: Restart Apex Language Servercommand to restart the Apex Language Server. (PR #6177) - Code coverage colors now match your VS Code theme, so you can create a personalized coding experience. In the past, these colors were static. (PR #6155)
Fixed
salesforcedx-vscode-core
- We made some changes under the hood. (PR #6163)
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We added telemetry to the Apex Language Server, so you can track all errors and exceptions. To see them, select the "Apex Language Server" dropdown in the Output tab. Want to enable or disable telemetry? Use the
Salesforcedx-vscode-core › Telemetrysetting. (PR #5897)
62.0.0 - October 9, 2024
Fixed
salesforcedx-vscode-apex
- We updated the Java Home Setting description to include Java 21. (PR #5878)
- We updated the Apex Language Server to support the latest features and improvements of the language. When you activate the new of the Apex extension for the first time, you could experience some lag while your workspace is upgraded to 252 Apex artifacts and your project is fully indexed. (PR #5887)
salesforcedx-vscode-core
- We fixed some labels in the Org Browser. (PR #5714) (PR #5844)
- We bumped SDR to catch up with the latest and fixed an issue where the
SFDX: Retrieve Source from Orgcommand nested a duplicate parent folder. Thank you Alan Reader for creating the issue. (PR #5889, ISSUE #2997)
Added
salesforcedx-vscode-apex
salesforcedx-vscode-apex-replay-debugger
salesforcedx-vscode-core
sa...
Release v63.6.0
63.6.0 - March 26, 2025
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
🚀 Agentforce for Developers Elevated to Salesforce Extension Pack
With its elevated presence in the Salesforce Extension Pack, Agentforce for Developers is now a core part of the Salesforce developer experience. This change improves discoverability, making it easier for developers to find and install Agentforce for Developers as part of their workflow. (PR #6097)
Fixed
salesforcedx-vscode-core
- We updated the org browser icon. (PR #6152)
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We added telemetry to the Apex Language Server, so you can track all errors and exceptions. To see them, select the "Apex Language Server" dropdown in the Output tab. Want to enable or disable telemetry? Use the
Salesforcedx-vscode-core › Telemetrysetting. (PR #5897)
62.0.0 - October 9, 2024
Fixed
salesforcedx-vscode-apex
- We updated the Java Home Setting description to include Java 21. (PR #5878)
- We updated the Apex Language Server to support the latest features and improvements of the language. When you activate the new of the Apex extension for the first time, you could experience some lag while your workspace is upgraded to 252 Apex artifacts and your project is fully indexed. (PR #5887)
salesforcedx-vscode-core
- We fixed some labels in the Org Browser. (PR #5714) (PR #5844)
- We bumped SDR to catch up with the latest and fixed an issue where the
SFDX: Retrieve Source from Orgcommand nested a duplicate parent folder. Thank you Alan Reader for creating the issue. (PR #5889, ISSUE #2997)
Added
salesforcedx-vscode-apex
salesforcedx-vscode-apex-replay-debugger
salesforcedx-vscode-core
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
salesforcedx-vscode-soql
- We made some changes under the hood. (PR #5889).
61.16.0 - October 2, 2024
Fixed
salesforcedx-vscode-soql
- We fixed an issue where the "Switch Between SOQL Builder and Text Editor" icon went missing. (PR #5868, ISSUE #5841)
61.15.0 - September 25, 2024
Added
salesforcedx-vscode-lwc
- To improve developer productivity and code quality, now you can use Salesforce TypeScript type definitions to develop Lightning web components (LWCs). For now, support for a limited number of Sal...
Release v63.5.0
63.5.0 - March 19, 2025
Fixed
salesforcedx-vscode-apex
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We added telemetry to the Apex Language Server, so you can track all errors and exceptions. To see them, select the "Apex Language Server" dropdown in the Output tab. Want to enable or disable telemetry? Use the
Salesforcedx-vscode-core › Telemetrysetting. (PR #5897)
62.0.0 - October 9, 2024
Fixed
salesforcedx-vscode-apex
- We updated the Java Home Setting description to include Java 21. (PR #5878)
- We updated the Apex Language Server to support the latest features and improvements of the language. When you activate the new of the Apex extension for the first time, you could experience some lag while your workspace is upgraded to 252 Apex artifacts and your project is fully indexed. (PR #5887)
salesforcedx-vscode-core
- We fixed some labels in the Org Browser. (PR #5714) (PR #5844)
- We bumped SDR to catch up with the latest and fixed an issue where the
SFDX: Retrieve Source from Orgcommand nested a duplicate parent folder. Thank you Alan Reader for creating the issue. (PR #5889, ISSUE #2997)
Added
salesforcedx-vscode-apex
salesforcedx-vscode-apex-replay-debugger
salesforcedx-vscode-core
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
salesforcedx-vscode-soql
- We made some changes under the hood. (PR #5889).
61.16.0 - October 2, 2024
Fixed
salesforcedx-vscode-soql
- We fixed an issue where the "Switch Between SOQL Builder and Text Editor" icon went missing. (PR #5868, ISSUE #5841)
61.15.0 - September 25, 2024
Added
salesforcedx-vscode-lwc
- To improve developer productivity and code quality, now you can use Salesforce TypeScript type definitions to develop Lightning web components (LWCs). For now, support for a limited number of Salesforce type definitions is in developer preview. To learn more, see TypeScript Support for LWC (Developer Preview).
salesforcedx-vscode-core
Fixed
salesforcedx-vscode-core
-
To help you quickly connect to the right default org, we’ve added handy indicators to let you know if your default org has expired, or isn’t valid. (PR #5835)
-
We fixed an ...
Release v63.4.1
63.4.1 - March 14, 2025
Fixed
salesforcedx-vscode-apex
-
We fixed an issue that caused missing descriptions to be handled incorrectly when creating an OpenAPI document. (PR #6125)
-
We improved the OpenAPI document generation so that the generated fields appear in a specific order. (PR #6129)
-
We made some changes under the hood. (PR #6140)
salesforcedx-vscode-core
-
We added some labels in the Org Browser. (PR #6139)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #6141)
63.2.3 - February 28, 2025
Added
salesforcedx-vscode-apex
- 🚀 Create Custom Agent Actions from Your Apex REST Classes using the new
SFDX: Create OpenAPI Document from this Class (Beta)command. The command generates an OpenAPI document for your Apex REST class using Salesforce's secure, custom generative AI model. Easily deploy the generated document to your org's API Catalog. Then, use it to create an agent action using Agent Studio. (PR #6102)
Fixed
salesforcedx-vscode-apex
- We corrected the URL for the "Set your Java version" link. (PR #6106)
63.1.1 - February 19, 2025
Added
salesforcedx-vscode-core
- We updated our dependencies to support the latest metadata types. As a result, you can now deploy all the latest metadata types using the VSCode extensions. (PR #6083)
63.0.0 - February 13, 2025
Added
salesforcedx-vscode-apex
- We've made some updates to the Apex LSP to prepare for an upcoming Salesforce release bump.(PR #6062)
Fixed
salesforcedx-utils-vscode
- We fixed an under-the-hood issue with our telemetry. (PR #6006)
salesforcedx-vscode
- Our VS Code Marketplace page now shows the minimum VS Code version that’s required by the Salesforce Extension Pack.(PR #6044)
62.14.1 - January 15, 2025
Fixed
salesforcedx-vscode-core
-
We got rid of that pesky warning that you saw every time you opened the
sfdx-project.jsonfile in your project. (PR #6000)
62.13.0 - January 8, 2025
Fixed
salesforcedx-utils-vscode
- We updated the configuration used to check if telemetry is enabled from
enableTelemetrytotelemetryLevel. (PR #5986)
62.12.0 - January 1, 2025
Fixed
salesforcedx-visualforce-language-server
- We fixed an issue where the Visualforce Language Server threw a
Request textDocument/documentHighlight failed with message: Debug Failure. False expression. Code: -32603error when JavaScript code in the embedded<script>tag was selected. Thank you AndrewStopchenko-SO for this contribution. (PR #5975)
62.9.1 - December 12, 2024
Added
salesforcedx-vscode-apex
- We've added a new VS Code configuration that lets you enable error telemetry from the Apex Language Server. We turned off this feature by default so that we can reduce noise. (PR #5969)
Fixed
salesforcedx-vscode-core
- We fixed some labels in the Org Browser.(PR #5967)
62.5.1 - November 14, 2024
Added
salesforcedx-vscode-apex
- We improved the accuracy of the range for Class, Enum, and Interface symbols in the Apex LSP
.jarfile. We also modified document symbol creation to introduce a nested symbol hierarchy in the Outline View, improving clarity of the outline. (PR #5945)
salesforcedx-vscode-core
- When you push or deploy on save, you’ll no longer automatically switch to the output panel view by default. You can toggle this setting with the
salesforcedx-vscode-core.push-or-deploy-on-save.showOutputPanelsetting. Thank you Jason Venable for this contribution. (PR #5904) - We made some changes under the hood. (PR #5939)
Fixed
salesforcedx-vscode-core
- To ensure smooth operation the Salesforce Extension Pack needs to run with a minimum supported Visual Studio Code version. We support only Visual Studio Code 1.90.0 or higher. (PR #5937)
62.3.1 - November 1, 2024
Fixed
salesforcedx-vscode-apex
-
We fixed a bug where deleted folders still showed Apex tests in the Testing sidebar. Now, when you delete a folder, it will be completely removed. No more pesky leftover tests! We did this by adding a new file watcher that triggers when an entire folder is deleted. (PR #5901)
-
🚀 We improved the startup time of the Apex extension by 30%. This was achieved by moving our check for orphaned Apex Language Server instances outside the activation loop. This means that Apex extensions start up faster, so you can get to work more quickly. (PR #5900)
-
We made some changes under the hood. (PR #5930)
62.2.0 - October 23, 2024
Added
salesforcedx-vscode-apex
- We added telemetry to the Apex Language Server, so you can track all errors and exceptions. To see them, select the "Apex Language Server" dropdown in the Output tab. Want to enable or disable telemetry? Use the
Salesforcedx-vscode-core › Telemetrysetting. (PR #5897)
62.0.0 - October 9, 2024
Fixed
salesforcedx-vscode-apex
- We updated the Java Home Setting description to include Java 21. (PR #5878)
- We updated the Apex Language Server to support the latest features and improvements of the language. When you activate the new of the Apex extension for the first time, you could experience some lag while your workspace is upgraded to 252 Apex artifacts and your project is fully indexed. (PR #5887)
salesforcedx-vscode-core
- We fixed some labels in the Org Browser. (PR #5714) (PR #5844)
- We bumped SDR to catch up with the latest and fixed an issue where the
SFDX: Retrieve Source from Orgcommand nested a duplicate parent folder. Thank you Alan Reader for creating the issue. (PR #5889, ISSUE #2997)
Added
salesforcedx-vscode-apex
salesforcedx-vscode-apex-replay-debugger
salesforcedx-vscode-core
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
salesforcedx-vscode-soql
- We made some changes under the hood. (PR #5889).
61.16.0 - October 2, 2024
Fixed
salesforcedx-vscode-soql
- We fixed an issue where the "Switch Between SOQL Builder and Text Editor" icon went missing. (PR #5868, ISSUE #5841)
61.15.0 - September 25, 2024
Added
salesforcedx-vscode-lwc
- To improve developer productivity and code quality, now you can use Salesforce TypeScript type definitions to develop Lightning web components (LWCs). For now, support for a limited number of Salesforce type definitions is in developer preview. To learn more, see TypeScript Support for LWC (Developer Preview).
salesforcedx-vscode-core
Fixed
salesforcedx-vscode-core
-
To help you quickly connect to the right default org, we’ve added handy indicators to let you know if your default org has expired, or isn’t valid. (PR #5835)
-
We fixed an issue where the
SFDX:Push Source to Default OrgandSFDX:Pull Source from Default Orgcommands would hang without throwing an error message when the error wasn’t related to files in the project. (PR #5838) -
We made some changes under the hood. ([PR #5857](https...