Illuminated Cloud Announcements

2.4.2.4 Issue 2980 - IC now displays the project's .aerrc file contents, if present, in the Apex test run configuration editor so that it's obvious exactly what command-line options will be used when executing Apex tests via aer. It's still possible to configure additional aer command-line options on a per-run config basis in the run configuration editor as well. Issue 2924 - Added a new deployment Apex test level, RunDependentTests , that is conceptually similar to RunRelevantTests , but the set of tests to be executed is computed by IC before deployment — and then executed using the RunSpecifiedTests test level — instead of being computed by the Salesforce server. There are notable differences in how IC computes transitive dependents vs. how Salesforce computes them (at least at present): IC specifically computes dependent relationships with member-level granularity whereas Salesforce computes them with class-level granularity. This means that if an intermediate dep...

2.4.2.3 Issue 2885 - Added support for additional decomposed metadata types . As with the underlying feature, this support is beta . If you encounter issues with it, consider disabling optional decomposition and please report those issues to Salesforce or IC as appropriate. Issue 2936 - Added support for both types of edition values in project-scratch-def.json files. Values are still written in the documented form when scratch org definition files are written by IC. When Apex Execution Runtime (aer) is used for Apex code coverage, IC now uses the covered line information instead of computing its own set of executable lines. The tooltip for the Salesforce skills Update button in the Agentforce configuration tab now includes details about the nature of the recommended update, e.g., the installed and available version date/time stamps. Improved the offline symbol table generator's support for ExternalServiceRegistration classes which can sometimes yield HTTP 500/Internal Serve...

2.4.2.2 Issue 3011 - Prospective fix for an IDE freeze during initial dynamic file type determination. The Apex Unresolvable Reference code inspection now verifies property accessor visibility based on the reference context with write expressions being checked against the property setter and read expressions being checked against the property getter. This becomes particularly useful in Winter '27 where the Apex Symbol API includes property getter and setter visibility information for properties of system types. The Apex Annotation and Modifier Agreement code inspection now flags property accessors with higher visibility than their containing properties as errors with quick fixes to adjust the property or property accessor visibility to a valid value relative to the other.

2.4.2.1 Removed support for JetBrains 2025.2 IDEs. Please make sure that you're using 2025.3+ (ideally the latest-and-greatest which is currently 2026.2.2) for continued IC plugin updates. Issue 3019 - Fixed a problem with commas in ApexDoc @see description text being interpreted incorrectly as a comma-delimited list of targets. Issue 3020 - Fixed a potential deadlock calculating the server time offset during the first Deploy Modified Metadata action against a specific connection after starting the IDE. Added support for per-test code coverage in aer. This is accessed using the IDE's standard per-test coverage feature. Note that you must be using aer 1.4+, and you must explicitly enable the feature in Illuminated Cloud | Configure Application | Apex | Apex Execution Runtime (aer) | Enable coverage by test . Integrated broad improvements in the OST's Apex system types based on the upcoming Apex Symbol API . In this version, IC does not yet use that API - it will be ...

2.4.2.0 This is a quick hotfix for a regression introduced in 2.4.1.9 . I've primarily been working closely with Salesforce to validate the upcoming Apex Symbol API as a way to improve the fidelity and performance of IC's OST generation. Issue 3018 - Fixed a regression where Compare With Server on a single file would result in multiple diffs being shown including the selected file and the intermediate temporary directories. Note that support for 2025.2 JetBrains IDEs will be removed soon, likely in next week's build. Please make sure that you're using 2025.3+ for the best experience going forward.

2.4.1.9 Issue 2983 - When rerunning individual test classes or methods from the test results tool window, the test execution engine that produces those results, either Salesforce org or aer, is used to filter the available test execution actions. Note that the IDE's default test executor cannot be filtered and is always offered, but if selected within a short time after showing the context menu for a test class or method in the test results view, the test execution engine for that view will be used. Issue 3008 - If a metadata retrieval is requested for immediate population of project files (as opposed to retrieve-for-merge or compare-with-server) and its payload includes files that were not explicitly part of the original request, also exist locally in the project, and are different from their local counterparts, the user is now notified and retrieve-for-merge behavior is used to allow careful reconcilation of these unrequested changes. Issue 3012 - Improved the previously-stubb...

2.4.1.8 Issue 2957 - Fixed an issue where errors could occur when adding/removing Apex offline debugger server-side checkpoints. Issue 3002 - Fixed an issue with @NamespaceAccessible symbols from installed managed packages with the same namespace as the org not being properly rendered into the OST. Note that you must regenerate your OST to see the effect of this fix. Issue 3003 - Fixed an issue where file copy/paste-for-overwrite in the IDE could result in IC prompting to remove the corresponding metadata files from the subscription and org. This is because the IDE actually does remove the original files and create new replacement files. IC now ignores the file removal events in this specific scenario. Issue 3004 - By default large numeric values are returned by the SOQL and SOSL query APIs in scientific notation , and the SOQL Query and SOSL Query tool windows simply show the returned data. Now those tool windows include a configuration option, Convert scientific notation value...