2.4.2.6 release notes

2.4.2.6

  • Issue 3007 - Winter '27 / API v68.0 update
    • Updated the SOAP client for API v68.0.
    • Updated the API version used for primary communication with Salesforce APIs to 68.0.
    • Added 68.0 as an available API version number for configured connections.
    • Updated metadata.xsd based on the API v68.0 Metadata API SOAP WSDL.
    • Updated the OST version number to prompt regeneration for system API changes in Winter '27.
    • Updated the bundled completions?type=apex Tooling REST API response to be based on the API v68.0 REST endpoint. See below for more information about support for the new Apex Symbol API.
    • Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Winter '27 changes.
    • Updated the bundled SLDS CSS and SVG icons to 2.264.1.
    • Updated for new org features, standard value set names, metadata XML file type extensions, etc.
    • Updated all integrated API documentation.
    • Added support for the new Apex Symbol API when generating project offline symbol tables.
      • This feature is currently in beta, so it is disabled by default.
      • This integration includes new configuration options in Illuminated Cloud | Configure Application | Other | Offline symbol table generation for whether or not to use the Apex Symbol API during OST generation:
        • System types - When unchecked (default), the Tooling API's completions?type=apex REST resource is used, though its output has been refined significantly based on the Apex Symbol API response. When checked, the Apex Symbol API's builtin category is queried, though its response is also refined based on observed issues and inconsistencies, all of which have been reported to Salesforce. The Apex Symbol API includes more information about annotations and modifiers, property accessors, and even ApexDoc-style documentation. It's also significantly faster than the Tooling API's completions?type=apex REST resource, so enabling this option can often improve OST generation times significantly.
          • Use bundled system type documentation - When checked, the bundled documentation for system types is used instead of the API-reported documentation. The bundled documentation for system types can often be more complete — both content and formatting — than the API-reported documentation. Disabled by default.
        • Custom types - When unchecked (default), custom Apex types from installed packages and other types that don't exist locally in the project are queried using the Partner and Tooling APIs. When checked, the Apex Symbol API's database category is queried. Note that I have observed a number of issues with this specific category where valid types are not included in the response due to compilation issues and even internal server errors.
        • Dynamic types - When unchecked (default), the DataWeaveScriptResource type's inner classes are populated based on the local project's *.dwl files, and classes in the ExternalService namespace are populated based the corresponding entries in the Salesforce Setup UI's Custom Code | Apex Classes | Dynamic Apex Classes section. When checked, the Apex Symbol API's dynamic category is queried for population of these types which includes everything in that same Dynamic Apex Classes section. Note that DataWeaveScriptResource inner type names now reflect the associated script names exactly and are no longer capitalized.
      • My recommendation: At present, I recommend enabling only System types and Dynamic types because of the errors I've seen with Custom types. If doing so results in missing or invalid OST entries, please disable them and report the specific issues to me so that I can work with Salesforce to resolve them. As these issues are addressed by Salesforce, I will update my recommendation, and ultimately I hope to enable the Apex Symbol API as the default setting and eventually remove support for the replaced APIs.
    • Added a Show Web Console... action to the Illuminated Cloud context menu that opens the new Web Console in the project's associated organization. The Web Console must, of course, be enabled in the org, and IC must first open another org page, specifically the Web Console Settings page, to ensure an active browser session before opening Web Console in a second tab. If you see Page doesn't exist in the resulting Web Console tab, please enable the feature in the Web Console Settings tab. I will continue to investigate ways to avoid having to open an additional tab if possible.
    • Added an Apex API version code inspection that flags Apex source files with an API version under 9.0 as invalid (errors), and those and in the range 9.0–19.0 as being scheduled for retirement (warnings), both with a quick fix to update the API version based on the project configuration.
    • Apex compiler warnings reported during deployment are now displayed in a notification.
    • Added support for the @BeforeClass annotation for Apex integration tests including support for generating @BeforeClass methods in integration test classes that do not current include them.
    • Added full support for the SOQL SET OPTIONS clause.