2.3.6.2 release notes

2.3.6.2

  • Issue 2798 - Summer '25 / API v64.0 update
    • Updated the SOAP client for API v64.0.
    • Updated the API version used for primary communication with Salesforce APIs to 64.0.
    • Added 64.0 as an available API version number for configured connections.
    • Updated metadata.xsd based on the API v64.0 Metadata API SOAP WSDL.
    • Updated the OST version number to prompt regeneration for system API changes in Summer '25.
    • Updated the bundled completions?type=apex Tooling REST API response to be based on the API v64.0 REST endpoint.
    • Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '25 changes.
    • Updated the bundled SLDS CSS and SVG icons to 2.27.1.
    • Updated for new org features, standard value set names, metadata XML file type extensions, etc.
    • Updated all integrated API documentation.
    • Added support for LWC local dev preview for a single LWC component. This manifests as another context action, Start local development server for componentName, when activated in the context of an LWC bundle file. Please make sure that the lightning-dev Salesforce CLI plugin is updated to the pre-release version if you wish to use this feature.
      NOTE: I've only seen this work for the absolute simplest of components. Those that use other components — including standard LWC components — or that use the LWC API from JavaScript/TypeScript fail to render. This is mentioned by Salesforce in the docs linked above and is due to the very early beta nature of this feature.
    A few additional notes about this release and Summer '25 / API v64.0:
    • I'm once again seeing quite frequent failures in certain orgs from the Salesforce Tooling completions?type=apex REST API that is used during OST generation to describe the standard Apex types. I have reported this to Salesforce already. If/when this happens, IC will automatically use a bundled version of that API response for the generated OST.
    • I have not yet integrated SLDS Linter. It looks like it can be integrated as rulesets for ESLint and Stylelint, though. Assuming so, I plan to integrate it that way with IC assisting with installation and configuration of the respective rulesets. If not, I will integrate SLDS Linter similar to how Salesforce Code Analyzer 5 has been integrated.
  • Issue 2799 - Added Apex reserved word import as an allowed Apex identifier name.
  • Made necessary changes for LSP4IJ 0.14.0. Note that automatic language server registration will no longer work with earlier versions of LSP4IJ, so please make sure that you're using 0.14.0 or higher with IC if using LSP4IJ in Community Edition IDEs.