Illuminated Cloud Announcements

2.4.1.6 - Hotfix for 2.4.1.5 Issue 3001 - For some reason the compiler marked the catch block for UnexpectedErrorFault as invalid in IC's expired/invalid session handling logic, so I removed it. Sure enough, though, that exception still occurs, and now IC wasn't handling and recovering from it properly any longer. This is a targeted hotfix to restore that handling, albeit in a manner that the compiler no longer flags.

2.4.1.3 Issue 2987 - Fixed several issues with Flow diagrams in 2026.2. While diagrams now render properly, there are still a few remaining issues that seem attributable to the newer version of Mermaid used by the 2026.2+ version of the Mermaid plugin: Icons do not display properly, so they're not included in diagram nodes. The diagram look-and-feel options, e.g., Elk renderer and curve styles, don't seem to have any effect. Fixed several issues with copying Apex string literal contents to the system clipboard that were introduced with Apex multiline string support. A quick reminder that the public issue tracker , user guide , and discussions have been completely migrated from Bitbucket and Google Groups respectively into GitHub. The original public issue tracker and user guide will be removed by Atlassian on August 20, 2026 as part of its sunsetting of Bitbucket Cloud issues and wikis , and the original discussion groups are now read-only historical archives given that the o...

2.4.0.9 Issue 2979 - Fixed an issue that could cause the derived invokable declaration index to fail indexing, resulting in constant "Analyzing" behavior. Added support for aer-based integration test execution with aer 1.2.0 +. Added support for Agent Script's subagent directive type including code completion, reference navigation, syntax highlighting, etc. Fixed an issue where class methods weren't being included in System.Label variant completions.

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.3.9.8 Hotfix for a few issues introduced in  2.3.9.7 : Issue 2933  - Fixed an NPE that could occur when running the Apex Offline Debugger for a full Apex unit test class. Issue 2934  - Fixed all known issues with aer-based unit test execution/debugging/coverage in projects with a namespace.

2.3.8.3 Reissue of  2.3.8.2  with a hotfix for an issue with LWC template braced expressions for event handler attributes. Issue 2868  - Improved filtering of LWC attributes displayed for code completion and integrated component documentation so that only public,  @api -decorated, writable fields/properties are included. If you find that something is no longer included that should be, please provide a concrete example and I'll be happy to address the omission. Issue 2869  - Fixed an issue with generation of  .illuminatedCloud/lwc/types  definitions when there are multiple metadata files with the same name, e.g., multiple  CustomLabels.labels-meta.xml  files. Issue 2870  - Fixed an issue where cross-metadata references could be added incorrectly for SObject fields with the same name in another SObject type. Issue 2873  - Fixed return types of  reportValidity()  methods and fixed names of  setCustomValidityForField() ...

2.3.8.0 Reissue of  2.3.7.9  with a hotfix for a potential NPE during retrieve-for-merge that I observed when testing something else almost immediately after release. Issue 2864  - Implemented a performance optimization during post-retrieve metadata files population so that bundles are only reconciled once per-bundle directory instead of once per-bundle content file. Fixed an issue with metadata subscription management where placeholder  *.object-meta.xml  files would be processed incorrectly resulting in the entire SObject type being added to the subscription when only children of that type are actually subscribed. Added warnings to indicate clearly that native connections should now be considered deprecated and will  no longer be supported  starting in Summer '27. IC will continue to support native connections as long as the underlying API is still available, but users are  strongly encouraged  to migrate from native connections to  OA...

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

2.3.5.5 This is a small, tactical hotfix build for a few issues found in  2.3.5.4  and/or the JetBrains 2025.1 updates. Issue 2766  - Fixed an issue with the new HTTP Client Salesforce API invocation feature that could occur when some connection configurations are invalid and/or incomplete. Issue 2768  - Fixed an issue with the Agentforce for Developers Dev Assistant tool window in 2025.1 attributable to a breaking plugin SDK change that I have already  reported  to JetBrains. Issue 2769  - Note that there also seems to be an issue with the Agentforce for Developers inline autocompletion API at present that I have already  reported  to Salesforce.  

2.3.3.4 Reissue of  2.3.3.3  with a hotfix for an issue where the new Local Development Server run configuration producer would cause actions from other run configuration producers — including those for Apex unit test execution — not to be added properly. Sincere apologies for those affected by this temporary regression.

2.3.2.5 Hotfix for  2.3.2.4  with the following fix: Issue 2610  - Fixed a regression with explicitly-configured Apex unit test run configurations from 2.3.2.4. Note that affected run configurations — specifically those that have been executed under this bug — will likely need to be reconfigured after updating to this change because the bug would remove configured test class information in-place instead of in a working version.  

2.3.1.8 Reissue of  2.3.1.7  with the fix for a potential error resulting from a stale cache entry when collecting transitive dependencies/dependents for Apex unit test execution and/or coverage analysis. 

2.3.1.4 (hotfix) This is effectively  2.3.1.3  with a hotfix for the customer-identified deployment issue described below. Issue 2570  - Fixed an issue that would result in  Check Only  (aka, "Dry Run") deployments actually updating the requested metadata in source format projects. This was due to the  sfdx  command's  -c  argument not being properly migrated to the corresponding  sf  command's  --dry-run  argument in the recent update to use the newer command set.

  2.3.1.1 (reissue of  2.3.1.0  with a critical bug fix) Fixed an NPE that would occur when configuring a brand new project for its connection, resulting in a blank IC2 project configuration screen. Sincere apologies for such a heinous oversight! Also note that I have already addressed both described shortcomings of the new deploy-before-test feature described below. Next week's build will fix the issue with a push cancelled due to conflict detection and add support for multi-module projects. 2.3.1.0 Issue 579  - Added a new Apex unit testing configuration option,  Illuminated Cloud | Configure Application | Unit Tests and Code Coverage | Unit Tests | Deploy before running unit tests  ( disabled  by default), that, when enabled, attempts to bring the Salesforce organization up to date before starting unit test execution for the requested set of Apex test classes/methods. The Salesforce organization is updated according to the project type and connectio...

  2.2.7.3  - reissue of  2.2.7.2  with hotfix for  issue 2380 . Issue 2380  - Fixed what appears to be a corner-case issue where the batch deploy/retrieve/delete dialog would fail when local foldered metadata files are found in a specific state. NOTE:  I've also noticed an intermittent issue when running some CLI commands where the JSON output of the command is malformed due to an error rolling the  sf.log  file. The specific command that seems to produce this most often for me is  force:project:create . In that situation, the resulting project is created, but the new project wizard stumbles due to the perceived issue. It's safe to open the created project and proceed with its configuration. I have logged this issue with Salesforce as  2209 .

  2.2.6.7  - reissue of  2.2.6.6  with fix for mismatched lightweight file type name for the JavaScript "improved syntax highlighting" file type for Community Edition IDEs. This is effectively a hotfix for  2.2.6.5  with the following fixes and small improvements: Fixed an issue where the  Tab / Shift+Tab  handling for ApexDoc Markdown list items would actually cause those keystrokes to be ignored elsewhere. Added ApexDoc Markdown fenced code block syntax highlighting in the editor and quick doc preview for file types which are not provided in a first-class manner in the host JetBrains IDE, e.g., JavaScript and CSS in Community Edition IDEs, as long as there is a corresponding abstract/lightweight file type for that language registered with the IDE. In support of the change above, I restored the old lightweight "improved syntax highlighting" file types for JavaScript and CSS to be used specifically for that purpose, though for those using a Commun...

  2.2.6.6 This is effectively a hotfix for  2.2.6.5  with the following fixes and small improvements: Fixed an issue where the  Tab / Shift+Tab  handling for ApexDoc Markdown list items would actually cause those keystrokes to be ignored elsewhere. Added ApexDoc Markdown fenced code block syntax highlighting in the editor and quick doc preview for file types which are not provided in a first-class manner in the host JetBrains IDE, e.g., JavaScript and CSS in Community Edition IDEs, as long as there is a corresponding abstract/lightweight file type for that language registered with the IDE. In support of the change above, I restored the old lightweight "improved syntax highlighting" file types for JavaScript and CSS to be used specifically for that purpose, though for those using a Community Edition IDE who prefer the syntax highlighting afforded by those file types over that provided by the respective TextMate bundles, they can be used instead.

  2.2.4.6  - Hotfix for  2.2.4.5 Issue 2245  - Fixed an issue with the new project wizard for metadata format projects where the full list of metadata would not be shown properly in the subscription editor once a connection is selected. This was an accidental regression introduced as a side effect of the new  .forceignore  file support in 2.2.4.5.

  2.2.4.3  - Hotfix for  2.2.4.2 Issue 2227  - A (hopefully) very small number of users are seeing an issue with 2.2.4.2 failing to initialize. Unfortunately I did not (and still do not) see this behavior across a large matrix of OS and JetBrains IDE test configurations, but I apologize sincerely to those who have experienced the issue. The issue should be resolved by this hotfix. Hopefully needless to say, please let me know ASAP if you're still seeing it after updating.