Release v64.7.1

64.7.1 - July 31, 2025

Fixed

salesforcedx-utils-vscode

• @W-18793417 - modify o11yService to support extension specific telemetry configuration (PR #6354)

salesforcedx-vscode-apex

• @W-18793417 - modify o11yService to support extension specific telemetry configuration (PR #6354)

salesforcedx-vscode-core

• Launch extensions was not working (PR #6436)

Release v64.5.1

64.5.1 - July 18, 2025

Added

salesforcedx-vscode-core

• We made some changes under the hood. (PR #6400, PR #6395)

Fixed

salesforcedx-vscode-apex

• We fixed a bug that was causing Apex test diagnostics to appear under an "unknown" label in the Problems Tab. (PR #6405)

salesforcedx-vscode-core

• We fixed a bug where unsaved manifests were being created when the SFDX: Generate Manifest File command is escaped. (PR #6391)

• We made an improvement to the user experience in the org browser. Users no longer need to click the SFDX: Refresh Types button every time they switch between orgs; the metadata types for the new org are now populated automatically. (PR #6401)

• We improved the SFDX: Turn On Apex Debug Logs for Replay Debugger command so it doesn't call the sf data:create:record CLI command under the hood. With that change comes a huge performance improvement - now the command completes in about 1/3 of the original runtime! (PR #6386)

Release v64.3.0

64.3.0 - July 2, 2025

Fixed

salesforcedx-vscode-apex

• Under the cover changes (PR #6384),(PR #6374)

salesforcedx-vscode-apex-replay-debugger

• Under the cover changes (PR #6384)

Release v64.2.1

64.2.1 - June 25, 2025

Added

salesforcedx-sobjects-faux-generator

salesforcedx-utils-vscode

salesforcedx-vscode-apex

salesforcedx-vscode-soql

• We made some changes under the hood. (PR #6322, PR #6331)

Fixed

salesforcedx-vscode-apex

• We fixed an issue with the Apex Language Server that caused database corruption. (PR #6371)

salesforcedx-vscode-core

• We fixed an issue where refreshing of SObjects definition wouldn't stop when no default org was set. (PR #6367)

• We added a helpful 'No components retrieved' message in the Output Tab when a manifest that contains no valid components is retrieved. You're welcome! (PR #6357)

Release v64.1.0

64.1.0 - June 18, 2025

Fixed

salesforcedx-vscode-apex

• We made some changes under the hood. (#6353)

Release v64.0.3

64.0.3 - June 15, 2025

Fixed

salesforcedx-vscode-apex

• We fixed an issue so that the "Rename Symbol (F2)" function in Visual Studio Code now correctly renames symbols in an Apex file. Thank you Pawel Wozniak for creating the issue.
  (Issue #5613) (PR #6351)

salesforcedx-vscode-core

• We added support for the ContentTypeBundle metadata type in the Org Browser. You no longer need to use the CLI commands to retrieve this type. (PR #6348)

Release v63.16.3

63.16.3 - June 6, 2025

Fixed

salesforcedx-vscode-apex

• We resolved an issue that caused a run-time error when activating the Apex Language Server. (Issue #6317) (PR #6316)

63.15.1 - May 30, 2025

Added

salesforcedx-vscode-apex

• We modified the Apex language server restart behavior and added new options:

  From the status bar: Respects the configured Restart Behavior setting.

  • prompt: Prompts with Restart Only selected by default.

  • restart: Restarts immediately.

  • reset: Cleans Apex DB and restarts.

  From the command palette: Always prompts the user, with the selection prehighlighted based on the configured setting. (PR #6292)

Fixed

salesforcedx-vscode-core

• We made some changes under the hood. (PR #6302)

salesforcedx-vscode-apex

salesforcedx-vscode-soql

• Syntax highlighting now works correctly when the @isTest annotation is on the same line as the test method. (PR #6304)

63.14.1 - May 21, 2025

Fixed

salesforcedx-vscode-core

• We reverted the check we added in v63.11.0. The check limited the visibility of org-related SFDX commands to only valid files. We removed it due to performance issues on large projects. (PR #6289)
• We bumped the versions of the Salesforce shared libraries to support deploying and retrieving the WorkflowFlowAutomation metadata type. (PR #6280)
• We updated the SFDX: Turn Off Apex Debug Log for Replay Debugger command. Now it doesn't call the sf data:delete:record CLI command under the hood. This change significantly improves how fast the command runs. (#6259)

63.12.0 - May 7, 2025

Added

salesforcedx-vscode

salesforcedx-vscode-expanded

We removed the ESLint and Apex PMD extensions from the Salesforce Expanded Pack. Instead, we recommend that you use the ESLint and PMD engines included in the Salesforce Code Analyzer extension, which we also added to the Salesforce Standard Pack. To learn more about the Code Analyzer extension, go to https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/analyze-vscode.html.

If you’re already familiar with Code Analyzer v4 (which is soon reaching its end of life), use this document to migrate to Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/migrate.html.

If you use ESLint and have custom ESLint configurations, see this document to learn how to use and configure the ESLint engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-eslint.html. Code Analyzer v5 currently supports only ESLint v8.x, and not v9.x.

Similarly, if you use PMD and have custom PMD configurations, see this document to learn how to use and configure the PMD engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-pmd.html.

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 packageDirectories array of sfdx-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 Test command. 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 DigitalExperienceBundle metadata. (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 Server command 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 Server command 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 Server command 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

• We made some changes under the hood. (PR #6146, PR #6148, PR #6150)

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)

• We made some changes under the hood. (PR #6124, PR #6128)

salesforcedx-vscode-lightning

salesforcedx-vscode-lwc

• We made some changes under the hood. ([PR #6141](https://github.com/forc...

Release v63.15.1

63.15.1 - May 30, 2025

Added

salesforcedx-vscode-apex

• We modified the Apex language server restart behavior and added new options:

  From the status bar: Respects the configured Restart Behavior setting.

  • prompt: Prompts with Restart Only selected by default.

  • restart: Restarts immediately.

  • reset: Cleans Apex DB and restarts.

  From the command palette: Always prompts the user, with the selection prehighlighted based on the configured setting. (PR #6292)

Fixed

salesforcedx-vscode-core

• We made some changes under the hood. (PR #6302)

salesforcedx-vscode-apex

salesforcedx-vscode-soql

• Syntax highlighting now works correctly when the @isTest annotation is on the same line as the test method. (PR #6304)

63.14.1 - May 21, 2025

Fixed

salesforcedx-vscode-core

• We reverted the check we added in v63.11.0. The check limited the visibility of org-related SFDX commands to only valid files. We removed it due to performance issues on large projects. (PR #6289)
• We bumped the versions of the Salesforce shared libraries to support deploying and retrieving the WorkflowFlowAutomation metadata type. (PR #6280)
• We updated the SFDX: Turn Off Apex Debug Log for Replay Debugger command. Now it doesn't call the sf data:delete:record CLI command under the hood. This change significantly improves how fast the command runs. (#6259)

63.12.0 - May 7, 2025

Added

salesforcedx-vscode

salesforcedx-vscode-expanded

We removed the ESLint and Apex PMD extensions from the Salesforce Expanded Pack. Instead, we recommend that you use the ESLint and PMD engines included in the Salesforce Code Analyzer extension, which we also added to the Salesforce Standard Pack. To learn more about the Code Analyzer extension, go to https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/analyze-vscode.html.

If you’re already familiar with Code Analyzer v4 (which is soon reaching its end of life), use this document to migrate to Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/migrate.html.

If you use ESLint and have custom ESLint configurations, see this document to learn how to use and configure the ESLint engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-eslint.html. Code Analyzer v5 currently supports only ESLint v8.x, and not v9.x.

Similarly, if you use PMD and have custom PMD configurations, see this document to learn how to use and configure the PMD engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-pmd.html.

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 packageDirectories array of sfdx-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 Test command. 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 DigitalExperienceBundle metadata. (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 Server command 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 Server command 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 Server command 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

• We made some changes under the hood. (PR #6146, PR #6148, PR #6150)

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)

• We made some changes under the hood. (PR #6124, PR #6128)

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 ...

Release v63.14.1

63.14.1 - May 21, 2025

Fixed

salesforcedx-vscode-core

• We reverted the check we added in v63.11.0. The check limited the visibility of org-related SFDX commands to only valid files. We removed it due to performance issues on large projects. (PR #6289)
• We bumped the versions of the Salesforce shared libraries to support deploying and retrieving the WorkflowFlowAutomation metadata type. (PR #6280)
• We updated the SFDX: Turn Off Apex Debug Log for Replay Debugger command. Now it doesn't call the sf data:delete:record CLI command under the hood. This change significantly improves how fast the command runs. (#6259)

63.12.0 - May 7, 2025

Added

salesforcedx-vscode

salesforcedx-vscode-expanded

We removed the ESLint and Apex PMD extensions from the Salesforce Expanded Pack. Instead, we recommend that you use the ESLint and PMD engines included in the Salesforce Code Analyzer extension, which we also added to the Salesforce Standard Pack. To learn more about the Code Analyzer extension, go to https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/analyze-vscode.html.

If you’re already familiar with Code Analyzer v4 (which is soon reaching its end of life), use this document to migrate to Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/migrate.html.

If you use ESLint and have custom ESLint configurations, see this document to learn how to use and configure the ESLint engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-eslint.html. Code Analyzer v5 currently supports only ESLint v8.x, and not v9.x.

Similarly, if you use PMD and have custom PMD configurations, see this document to learn how to use and configure the PMD engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-pmd.html.

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 packageDirectories array of sfdx-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 Test command. 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 DigitalExperienceBundle metadata. (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 Server command 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 Server command 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 Server command 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

• We made some changes under the hood. (PR #6146, PR #6148, PR #6150)

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)

• We made some changes under the hood. (PR #6124, PR #6128)

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-v...

Release v63.12.0

63.12.0 - May 7, 2025

Added

salesforcedx-vscode

salesforcedx-vscode-expanded

We removed the ESLint and Apex PMD extensions from the Salesforce Expanded Pack. Instead, we recommend that you use the ESLint and PMD engines included in the Salesforce Code Analyzer extension, which we also added to the Salesforce Standard Pack. To learn more about the Code Analyzer extension, go to https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/analyze-vscode.html.

If you’re already familiar with Code Analyzer v4 (which is soon reaching its end of life), use this document to migrate to Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/migrate.html.

If you use ESLint and have custom ESLint configurations, see this document to learn how to use and configure the ESLint engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-eslint.html. Code Analyzer v5 currently supports only ESLint v8.x, and not v9.x.

Similarly, if you use PMD and have custom PMD configurations, see this document to learn how to use and configure the PMD engine of Code Analyzer v5: https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/engine-pmd.html.

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 packageDirectories array of sfdx-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 Test command. 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 DigitalExperienceBundle metadata. (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 Server command 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 Server command 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 Server command 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

• We made some changes under the hood. (PR #6146, PR #6148, PR #6150)

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)

• We made some changes under the hood. (PR #6124, PR #6128)

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 made some changes under the hood. (PR #5996, PR #6003)

• We got rid of that pesky warning that you saw every time you opened the sfdx-project.json file in your project. (PR #6000)

62.13.0 - January 8, 20...