2.3.7.8 release notes

2.3.7.8

Reissue of 2.3.7.7 with fix for issue 2866.

• Issue 2858 - Winter '26 / API v65.0 update
  • Updated the API version used for primary communication with Salesforce APIs to 65.0.
  • Added 65.0 as an available API version number for configured connections.
  • Updated the OST version number to prompt regeneration for system API changes in Winter '26.
  • Updated the bundled completions?type=apex Tooling REST API response to be based on the API v65.0 REST endpoint.
  • Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '26 changes.
  • Updated the bundled SLDS CSS and SVG icons to 2.28.0. Note that between this bundled SLDS update and the integration of SLDS Linter, IC should provide solid support for SLDS v2. If you find that there are missing/incomplete features around SLDS v2, please let let me know and I'll be happy to address them.
  • Updated for new org features, standard value set names, metadata XML file type extensions, etc.
  • Updated all integrated API documentation.
  • The Apex Annotation and Modifier Agreement code inspection has been updated to flag methods with the abstract and override modifiers as invalid if they don't also have an explicit non-private visibility modifier. These violations are reported as errors if the containing class is for API v65.0+ and as warnings if for an earlier API version. Quick fixes are provided to add a valid visibility modifier or to remove the abstract or override modifier (which may break related code, of course).
  • The following Winter '26-related items are not yet (fully) addressed, but I wanted to comment on their respective status:
    • As has become the norm, the new SOAP WSDLs are not available until a few days after the platform release is available in all orgs, so this build does not yet include a SOAP client or metadata.xsd based on API v65.0. As soon as the new WSDLs are available, I'll integrate them and provide a new IC build.
    • OpenAPI document generation - I am currently investigating how to integrate Salesforce's existing logic for OpenAPI document generation from Apex classes. Unlike most features, those are not provided via a SOAP/REST API or even the Salesforce CLI. However, I believe I have a good lead on how to access them and will provide corresponding first-class IDE actions as soon as I'm able to do so.
    • Dev Agent support - As referenced in earlier release notes, I am investigating how best to incorporate Dev Agent-type behavior into IC. At present I do not plan to build a full agent from scratch as there are already many strong offerings with first-class support for JetBrains' IDEs, and Salesforce has made their MCP server available to allow those offerings to interact safely and securely with connected Salesforce organizations. Please see the linked information for how best to add agentic AI features to your IDE with access to Salesforce's MCP server.
    • ApexGuru integration - ApexGuru is technically just another static code analyzer engine for Salesforce Code Analyzer which is already integrated tightly into IC. However, because that feature is only enabled in production and full sandbox organizations, I don't currently have access to an org where I can verify its behavior and address issues that might exist, if any. I am working with Salesforce to remedy that issue, though, and I will include any changes required for proper ApexGuru support in a future build.
• Issue 2866 - SOAP API login() is no longer available in API v65.0+, so IC always uses API v64.0 to call that specific API. All other APIs are called using the latest API version. NOTE: Those who use native IC connections are encouraged to use OAuth (or other CLI-managed) connections instead to ensure forward compatibility as it sounds like the login() API will be disabled completely as of Summer '27.
• Added support for standard message channels to both Aura and LWC.