Releases: forcedotcom/salesforcedx-vscode
Release v62.3.1
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 › Telemetry
setting. (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 version 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 Org
command 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 Org
andSFDX:Pull Source from Default Org
commands 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), (PR #5830), (PR #5786)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #5821)
61.12.0 - September 4, 2024
Fixed
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We fixed an issue where the
paths
property was incorrectly placed in jsconfig.json. (PR #597, PR #5798)
61.11.0 - August 28, 2024
Fixed
salesforcedx-vscode-core
- We fixed an issue that was causing the
SFDX: Generate Manifest File
command to appear in the context menu for manifest files. (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you [KevinGossentCap](https://github.com/KevinGossentCap...
Release v62.2.0
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 › Telemetry
setting. (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 version 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 Org
command 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 Org
andSFDX:Pull Source from Default Org
commands 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), (PR #5830), (PR #5786)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #5821)
61.12.0 - September 4, 2024
Fixed
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We fixed an issue where the
paths
property was incorrectly placed in jsconfig.json. (PR #597, PR #5798)
61.11.0 - August 28, 2024
Fixed
salesforcedx-vscode-core
- We fixed an issue that was causing the
SFDX: Generate Manifest File
command to appear in the context menu for manifest files. (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-c...
Release v62.0.0
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 version 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 Org
command 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 Org
andSFDX:Pull Source from Default Org
commands 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), (PR #5830), (PR #5786)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #5821)
61.12.0 - September 4, 2024
Fixed
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We fixed an issue where the
paths
property was incorrectly placed in jsconfig.json. (PR #597, PR #5798)
61.11.0 - August 28, 2024
Fixed
salesforcedx-vscode-core
- We fixed an issue that was causing the
SFDX: Generate Manifest File
command to appear in the context menu for manifest files. (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
th...
Release v61.16.0
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 Org
andSFDX:Pull Source from Default Org
commands 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), (PR #5830), (PR #5786)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #5821)
61.12.0 - September 4, 2024
Fixed
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We fixed an issue where the
paths
property was incorrectly placed in jsconfig.json. (PR #597, PR #5798)
61.11.0 - August 28, 2024
Fixed
salesforcedx-vscode-core
- We fixed an issue that was causing the
SFDX: Generate Manifest File
command to appear in the context menu for manifest files. (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. ([PR #5635](#563...
Release v61.15.0
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 Org
andSFDX:Pull Source from Default Org
commands 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), (PR #5830), (PR #5786)
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We made some changes under the hood. (PR #5821)
61.12.0 - September 4, 2024
Fixed
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We fixed an issue where the
paths
property was incorrectly placed in jsconfig.json. (PR #597, PR #5798)
61.11.0 - August 28, 2024
Fixed
salesforcedx-vscode-core
- We fixed an issue that was causing the
SFDX: Generate Manifest File
command to appear in the context menu for manifest files. (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. (PR #5635)
Fixed
salesforcedx-vscode-apex
- We fixed an issue where the output of the "Apex Code Coverage by Class" table in the Apex test results were missing when "Store Only Aggregated Code Coverage" is enabled in the Apex Test Execution settings. Thank you Matthias Rolke for brin...
Release v61.12.0
61.12.0 - September 4, 2024
Fixed
salesforcedx-vscode-lightning
salesforcedx-vscode-lwc
- We fixed an issue where the
paths
property was incorrectly placed in jsconfig.json. (PR #597, PR #5798)
61.11.0 - August 28, 2024
Fixed
salesforcedx-vscode-core
- We fixed an issue that was causing the
SFDX: Generate Manifest File
command to appear in the context menu for manifest files. (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. (PR #5635)
Fixed
salesforcedx-vscode-apex
- We fixed an issue where the output of the "Apex Code Coverage by Class" table in the Apex test results were missing when "Store Only Aggregated Code Coverage" is enabled in the Apex Test Execution settings. Thank you Matthias Rolke for bringing this to our attention. (PR #370, PR #5629)
salesforcedx-vscode-expanded
- We resolved an issue where the Apex PMD extension was missing from the Salesforce Extension Pack Expanded when published in the Open VSX Registry. (PR #5639)
60.15.0 - May 29, 2024
Added
Features
🚀 We’re thrilled to announce that Einstein for Developers (Beta) is now a part of the Salesforce Expanded Pack! 🚀
Here’s what you can expect with this change -
- Access to powerful generative AI tooling that is grounded in the context your org’s data, and is backed by the promise of Salesforce’s Trust Layer. See Additional Terms of Use for information.
- Seamless updating of extension versions. Weekly extension releases include new features and enhancements that we continue to make to Einstein for Developers!
- Einstein for Developers is enabled by default in our VS Code desktop application. Follow these steps to enable it in Code Builder.
We’re excited that we’ve made it easier for you to give Einstein for Developers a spin, and we hope you’ll give it a try. We’d love your feedback! 📝
Fixed
docs
- We made more prominent notes for known issu...
Release v61.11.0
61.11.0 - August 28, 2024
Added
salesforcedx-vscode-core
- Increase minimum vscode version to 1.86.0 (PR #5733)
Fixed
salesforcedx-vscode-core
- "SFDX: Generate Manifest File" command should not exist for manifest files (PR #5731)
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. (PR #5635)
Fixed
salesforcedx-vscode-apex
- We fixed an issue where the output of the "Apex Code Coverage by Class" table in the Apex test results were missing when "Store Only Aggregated Code Coverage" is enabled in the Apex Test Execution settings. Thank you Matthias Rolke for bringing this to our attention. (PR #370, PR #5629)
salesforcedx-vscode-expanded
- We resolved an issue where the Apex PMD extension was missing from the Salesforce Extension Pack Expanded when published in the Open VSX Registry. (PR #5639)
60.15.0 - May 29, 2024
Added
Features
🚀 We’re thrilled to announce that Einstein for Developers (Beta) is now a part of the Salesforce Expanded Pack! 🚀
Here’s what you can expect with this change -
- Access to powerful generative AI tooling that is grounded in the context your org’s data, and is backed by the promise of Salesforce’s Trust Layer. See Additional Terms of Use for information.
- Seamless updating of extension versions. Weekly extension releases include new features and enhancements that we continue to make to Einstein for Developers!
- Einstein for Developers is enabled by default in our VS Code desktop application. Follow these steps to enable it in Code Builder.
We’re excited that we’ve made it easier for you to give Einstein for Developers a spin, and we hope you’ll give it a try. We’d love your feedback! 📝
Fixed
docs
-
We made more prominent notes for known issue with trusted IP ranges for Code Builder. (PR #5606)
-
We updated the Code Builder content for licenses for add-ons ([PR #5605](https://github.com/forcedotcom/salesforcedx...
Release v61.10.0
61.10.0 - August 21, 2024
Added
salesforcedx-vscode
salesforcedx-vscode-expanded
- 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.86 or higher. (PR #5715)
salesforcedx-vscode-core
- Good news! We’ve made the core extension smaller and better. By bundling more libraries, we’ve reduced the size from 8.9MB to 2.8MB. That’s a big win for everyone. (PR #5705)
Fixed
docs
- We made some changes under the hood. (PR #5707)
salesforcedx-apex-replay-debugger
salesforcedx-vscode-apex-replay-debugger
- To give us better insight into its behavior, we’ve added more telemetry to the Apex Replay Debugger. (PR #5724)
salesforcedx-vscode
salesforcedx-vscode-expanded
- We made helpful clarifications in Marketplace READMEs. (PR #5716)
salesforcedx-vscode-core
-
We fixed an issue with the
SFDX: Diff Folder Against Org
andSFDX: Diff File Against Org
commands. These commands now work correctly when you have a file in your project, but not in your org. You won’t see a notification that says the command is running when it’s not. (PR #5722) -
You can now rename Lightning Web Component (LWC) components when the Aura folder isn’t present, and vice versa. We’ve also added checks when creating new LWC and Aura components to ensure that the name doesn't already exist. (PR #5718, ISSUE #5692)
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. (PR #5635)
Fixed
salesforcedx-vscode-apex
- We fixed an issue where the output of the "Apex Code Coverage by Class" table in the Apex test results were missing when "Store Only Aggregated Code Coverage" is enabled in the Apex Test Execution settings. Thank you Matthias Rolke for bringing this to our attention. (PR #370, PR #5629)
salesforcedx-vscode-expanded
- We resolved an issue where the Apex PMD extension was missing from the Salesforce Extension Pack Expanded when published in the Open VSX Registry. (PR #5639)
60.15.0 - May 29, 2024
Added
Features
🚀 We’re thrilled to announce that Einstein for Developers (Beta) is now a part of the Salesforce Expanded Pack! 🚀
Here’s what you can expect with this change -
- Access to powerful generative AI tooling that is grounded in the context your org’s data, and is backed by the promise of Salesforce’s Trust Layer. See Additional Terms of Use for information.
- Seamless updating of extension versions. Weekly extension releases include new features and enhancements that we continue to make to Einstein for Developers!
- Einstein for Developers is enabled by default in our VS Code desktop application. Follow these steps to enable it in Code Builder.
We’re excited that we’ve made it easier for you to give Einstein for Developers a spin, and we hope you’ll give it a try. We’d love your feedback! 📝
Fixed
docs
-
We made more prominent notes for known issue with trusted IP ranges for Code Builder. (PR #5606)
-
We updated the Code Builder content for licenses for add-ons (PR #5605)
salesforcedx-vscode-expanded
- We made updates to the guidelines for Einstein for Developers. (PR #5596)
60.13.0 - May 15, 2024
Fixed
docs
- We made updates to the troubleshooting guidelines for Einstein for Developers. ([PR #5587](https://github.com/forcedotcom/salesforcedx-vsc...
Release v61.8.1
61.8.1 - August 8, 2024
Added
salesforcedx-vscode-expanded
- The Code Analyzer extension is now part of our Expanded Pack. Use this extension to scan your code against multiple rule engines to produce lists of violations and improve your code. (PR #5702)
Fixed
salesforcedx-utils
salesforcedx-utils-vscode
- We fixed a bug that caused some CLI commands to return ANSI color characters in JSON results. This change removes those characters before the JSON strings are parsed. (PR #5708, ISSUE #5695)
salesforcedx-vscode-core
- We made some changes under the hood. (PR #5699)
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. (PR #5635)
Fixed
salesforcedx-vscode-apex
- We fixed an issue where the output of the "Apex Code Coverage by Class" table in the Apex test results were missing when "Store Only Aggregated Code Coverage" is enabled in the Apex Test Execution settings. Thank you Matthias Rolke for bringing this to our attention. (PR #370, PR #5629)
salesforcedx-vscode-expanded
- We resolved an issue where the Apex PMD extension was missing from the Salesforce Extension Pack Expanded when published in the Open VSX Registry. (PR #5639)
60.15.0 - May 29, 2024
Added
Features
🚀 We’re thrilled to announce that Einstein for Developers (Beta) is now a part of the Salesforce Expanded Pack! 🚀
Here’s what you can expect with this change -
- Access to powerful generative AI tooling that is grounded in the context your org’s data, and is backed by the promise of Salesforce’s Trust Layer. See Additional Terms of Use for information.
- Seamless updating of extension versions. Weekly extension releases include new features and enhancements that we continue to make to Einstein for Developers!
- Einstein for Developers is enabled by default in our VS Code desktop application. Follow these steps to enable it in Code Builder.
We’re excited that we’ve made it easier for you to give Einstein for Developers a spin, and we hope you’ll give it a try. We’d love your feedback! 📝
Fixed
docs
-
We made more prominent notes for known issue with trusted IP ranges for Code Builder. (PR #5606)
-
We updated the Code Builder content for licenses for add-ons (PR #5605)
salesforcedx-vscode-expanded
- We made updates to the guidelines for Einstein for Developers. (PR #5596)
60.13.0 - May 15, 2024
Fixed
docs
- We made updates to the troubleshooting guidelines for Einstein for Developers. (PR #5587)
salesforcedx-vscode-core
- We got rid of the annoying
"Warning: Ignoring extra certs from null, load failed: error:80000002:system library::No such file or directory"
warning when theSalesforcedx-vscode-core: NODE_EXTRA_CA_CERTS
setting is missing. (PR #5575)
60.12.0 - May 8, 2024
Added
salesforcedx-vscode-core
-
We made a major upgrade to the version of the @salesforce/core library. (PR #5556)
-
We no longer prompt you for a directory location when you use the context menu to run an Apex command to create a class. We just gather the information from the context, making things a little more convenient for you. Thank you Heber for this awesome contribution. #5544 (PR #5561)
Fixed
docs
- We updated the replay debugger content with some helpful information. (PR #5566)
60.11.0 - May 1, 2024
Fixed
salesforcedx-utils-vscode
- We made some changes under the hood. (PR #5540)
salesforcedx-vscode-apex
- An abstract method is now correctly displayed in the Outline view. (PR #5555, ISSUE #5553)
60.10.0 - April 24, 2024
Added
salesforcedx-vscode-lwc
- We now support the
lightning_UrlAddressable
enumeration type in LWC components. Thank you
Mike Senn for this contribution. (PR #5328)
Fixed
salesforcedx-apex-debugger
salesforcedx-utils
salesforcedx-utils-vscode
salesforcedx-vscode-apex-d...
Release v61.7.0
61.7.0 - July 31, 2024
Added
salesforcedx-vscode-core
- We made some changes under the hood.
61.6.0 - July 24, 2024
Added
salesforcedx-vscode-apex
salesforcedx-vscode-lwc
- Now you can collapse all Apex and LWC tests in the testing side panel. Thank you jamessimone for creating the PR. (PR #5684)
salesforcedx-vscode-apex
- We made a major upgrade to the
@salesforce/apex-node-bundle
library. With this upgrade, the Apex test results now display information about test setup methods and test setup time, improving your testing experience. (PR #5691).
Fixed
docs
- We've made some under-the-hood improvements to enhance security.(PR #5690)
61.5.0 - July 17, 2024
Added
salesforcedx-vscode-lwc
- We added support for the LWC Lightning Record Picker component. You can now use features like hover and auto-completion when you're working with this component in VS Code. (PR #5683).
61.4.0 - July 10, 2024
Added
salesforcedx-vscode-core
Fixed
- We fixed an issue that prevented extensions from activating when the beta feature to decompose components was used in
sfdx-project.json
. Thank you KevinGossentCap for reporting the issue. (PR #1359, ISSUE #5664)
61.2.1 - June 26, 2024
Added
salesforcedx-vscode-core
- 🚀 🚀 We're happy to announce that we've made our extension pack smaller and faster. We've bundled more Salesforce libraries that the extension pack depends on into the extension pack, which reduced its size by 40 MB. You should see substantial improvements in startup time and performance.
Fixed
docs
-
We updated our documentation with information about installing JDK 21. (PR #5655)
-
We made updates to our Apex Debugger documentation. (PR #5649)
salesforcedx-vscode-core
- We fixed an issue where an incorrect caching strategy caused metadata files to deploy with outdated content. (PR #5650, ISSUE #5612)
61.1.2 - June 21, 2024
Added
salesforcedx-vscode-apex
- We fixed an issue where
sf apex get test
andsf apex run test
threw heap out of memory in large projects. Thank you Paweł Idczak for creating the issue. (PR #5647, ISSUE #5589)
salesforcedx-vscode-apex-replay-debugger
- We made some changes under the hood. (PR #5647)
Fixed
docs
- We removed trailing slashes from URLs in docs to improve SEO. Thank you Jason Rogers for your work on this PR. (PR #5632)
salesforcedx-vscode-soql
- We fixed an issue where users were unable to filter by NULL values if the SObject field type was a string. (PR #5646)
61.0.1 - June 14, 2024
Added
salesforcedx-vscode-apex
-
🎉 We're excited to announce that our extensions now support Java 21! 🚀 (PR #5621)
-
Apex language server has been updated to support the latest features and improvements of the language. When you activate the new version of the Apex extension for the first time, there might be a noticeable delay while your workspace is upgraded to 250 Apex artifacts and your project is fully indexed. (PR #5635)
Fixed
salesforcedx-vscode-apex
- We fixed an issue where the output of the "Apex Code Coverage by Class" table in the Apex test results were missing when "Store Only Aggregated Code Coverage" is enabled in the Apex Test Execution settings. Thank you Matthias Rolke for bringing this to our attention. (PR #370, PR #5629)
salesforcedx-vscode-expanded
- We resolved an issue where the Apex PMD extension was missing from the Salesforce Extension Pack Expanded when published in the Open VSX Registry. (PR #5639)
60.15.0 - May 29, 2024
Added
Features
🚀 We’re thrilled to announce that Einstein for Developers (Beta) is now a part of the Salesforce Expanded Pack! 🚀
Here’s what you can expect with this change -
- Access to powerful generative AI tooling that is grounded in the context your org’s data, and is backed by the promise of Salesforce’s Trust Layer. See Additional Terms of Use for information.
- Seamless updating of extension versions. Weekly extension releases include new features and enhancements that we continue to make to Einstein for Developers!
- Einstein for Developers is enabled by default in our VS Code desktop application. Follow these steps to enable it in Code Builder.
We’re excited that we’ve made it easier for you to give Einstein for Developers a spin, and we hope you’ll give it a try. We’d love your feedback! 📝
Fixed
docs
-
We made more prominent notes for known issue with trusted IP ranges for Code Builder. (PR #5606)
-
We updated the Code Builder content for licenses for add-ons (PR #5605)
salesforcedx-vscode-expanded
- We made updates to the guidelines for Einstein for Developers. (PR #5596)
60.13.0 - May 15, 2024
Fixed
docs
- We made updates to the troubleshooting guidelines for Einstein for Developers. (PR #5587)
salesforcedx-vscode-core
- We got rid of the annoying
"Warning: Ignoring extra certs from null, load failed: error:80000002:system library::No such file or directory"
warning when theSalesforcedx-vscode-core: NODE_EXTRA_CA_CERTS
setting is missing. (PR #5575)
60.12.0 - May 8, 2024
Added
salesforcedx-vscode-core
-
We made a major upgrade to the version of the @salesforce/core library. (PR #5556)
-
We no longer prompt you for a directory location when you use the context menu to run an Apex command to create a class. We just gather the information from the context, making things a little more convenient for you. Thank you Heber for this awesome contribution. #5544 (PR #5561)
Fixed
docs
- We updated the replay debugger content with some helpful information. (PR #5566)
60.11.0 - May 1, 2024
Fixed
salesforcedx-utils-vscode
- We made some changes under the hood. (PR #5540)
salesforcedx-vscode-apex
- An abstract method is now correctly displayed in the Outline view. (PR #5555, ISSUE #5553)
60.10.0 - April 24, 2024
Added
salesforcedx-vscode-lwc
- We now support the
lightning_UrlAddressable
enumeration type in LWC components. Thank you
Mike Senn for this contribution. (PR #5328)
Fixed
salesforcedx-apex-debugger
salesforcedx-utils
salesforcedx-utils-vscode
salesforcedx-vscode-apex-debugger
- We fixed an issue where the ISV Debugger threw a project configuration error when you clicked the Launch Apex Debugger button. Now you should be able to start the debugger without any issues. We'd love to hear your feedback on the ISV Debugger, and happy debugging! (PR #5522)
salesforcedx-vscode-apex
salesforcedx-vscode-apex-replay-debugger
salesforcedx-vscode-core
60.8.0 - April 10, 2024
Added
forcedotcom/salesforcedx-apex
- We added detailed elapsed time debug log data as an investigative step in trying to diagnose Apex test commands that are taking a long time t...