Illuminated Cloud Announcements

2.4.0.8 Issue 2974 - Summer '26 / API v67.0 update Updated the SOAP client for API v67.0. Updated the API version used for primary communication with Salesforce APIs to 67.0. Added 67.0 as an available API version number for configured connections. Updated metadata.xsd based on the API v67.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Summer '26. Updated the bundled completions?type=apex Tooling REST API response to be based on the API v67.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '26 changes. Updated the bundled SLDS CSS and SVG icons to 2.30.4. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Usages of SOQL WITH SECURITY_ENFORCED in Apex source files with API version 67.0+ are now flagged as errors with a quick-fix to use WITH USER_MODE instead. Apex classes with...

2.4.0.7 Minor bug fix release before next week's Summer '26 updates: Issue 2968 (redux) - Improved fix for an NPE when copy/pasting files to the IDE project. Issue 2972 - Addressed an potentially significant IDE memory growth issue introduced accidentally in the last few builds where IC's server metadata index could be included once per-file in what should otherwise be a very slim file-to-metadata cache. Several other minor fixes. Also, if you are having issues with validation and code completion in Salesforce metadata XML files in 2026.1, it appears to be a regression in the base JetBrains IDE, and I've logged a bug in their public issue tracker that clearly shows the correct behavior in 2025.3 and earlier and incorrect behavior in 2026.1.

2.4.0.6 Issue 2964 - Fixed an issue where AbstractFileType files were being processed incorrectly during indexing. Issue 2965 - Fixed an issue where compiled LWC TypeScript *.js files weren't being properly added to deployment payloads. Issue 2966 - Increased the LWC TypeScript compilation timeout from 30 seconds to 5 minutes. If you still see TypeScript compilation timeouts, please let me know so that I can either raise it further or make it configurable. Issue 2968 - Prospective fix for an NPE when copy/pasting files to the IDE project. I say "prospective" because I've not been able to reproduce it, but the nature of the NPE is clear from the stack trace, and I've updated that logic to be defensive and use the original, non-null parameter value when necessary. Implemented a number of quality-of-life fixes and improvements: With the changes to IC in 2.4.0.5 to accommodate for how CLI-based connection access tokens are made available to clients, it was nece...

2.4.0.5 Salesforce CLI issue 3560 - IMPORTANT: The Salesforce CLI is in the process of implementing a set of security mitigation changes, some of them with breaking behavior . Starting with this build, IC accommodates for the changes around how connection access tokens are made available via CLI commands. For pre-2.136.8 CLI versions, IC will use continue to the org list and org display commands to get CLI-based connection access tokens; for 2.136.8+ CLI versions, IC will use the org auth show-access-token command. IC automatically determines the installed CLI version and, for efficiency, caches that value aggressively, though it should be resilient to CLI upgrades/downgrades while running. In support of Salesforce's goal of not having access tokens stored in-the-clear in the file system, IC no longer caches them persistently across IDE sessions. They are still cached aggressively in-memory, but if/when the IDE is restarted, IC will need to fetch access tokens for CLI-based ...

2.4.0.4 Issue 2951 - Added first-class support for UI Bundles and Salesforce Multi-Framework . Note that this feature requires native IDE JavaScript/TypeScript/CSS/React support, so you'll need to pair Illuminated Cloud with either a commercial JetBrains IDE or a free 2026.1+ JetBrains IDE. A demonstration video is available here. As part of this work, the Illuminated Cloud application-level settings tab LWC has been renamed UI Frameworks and now includes options for configuration of both Lightning Web Components and UI Bundles behavior. The new/changed options are: LWC Enable LWC local development - LWC local development support has existed for some time, but it wasn't possible to disable it. Now it can be disabled if desired, but it is enabled by default . Disable deploy-on-save of LWC source files when the local development server is running - This option was moved from the Deployment tab (previously called Validation and Deployment ) to be closer to its related setti...

2.4.0.3 Issue 2919  (redux) and  Issue 2955  - Improved handling of references to  *-meta.xml  files when those files are renamed, particularly in other XML files such as  package.xml  and permission sets/profiles. Issue 2949  - Prospective fix for an issue where loaded scratch org definition files in the create scratch org dialog could be based on stale cached information. Issue 2952  - Improved Apex offline debugger source position determination when stub/synthetic declarations are involved, e.g., default no-arg constructors. Issue 2956  - Fixed an issue where Apex coverage would not be displayed properly after unit test execution. Extended IC's assisted installation/configuration support for agentic AI tools to include more agentic AI JetBrains plugins and more/more recent Salesforce-specific support components. A demonstration video is available  here . In  Illuminated Cloud | Configure Application | Agentforce , the  ...

2.4.0.2 Issue 2950  - Updated the  *scratch-org-def.json  JSON schema for the latest-and-greatest settings types. Added support for aer-based profiling of executed unit tests via the  Profile " Run Configuration Name " with aer  Apex unit test executor. After aer test execution, the resulting profiling snapshot is automatically opened in the  Perfetto trace viewer  for review. Note that aer is a different Apex runtime than the Salesforce server and will have different performance characteristics, though the resulting profiling data should hopefully be directionally useful. It can, of course, also be used to understand aer-based test execution hotspots and bottlenecks. To profile org-based execution, use the Salesforce server Apex unit test profiling executor and IC's Log Analyzer. Added another aer unit test execution configuration option to add the  --skip-errors  option always when aer is executed. This option is  enabled by default ...