Illuminated Cloud Announcements

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

2.4.1.7 Issue 2998 - IC no longer bundles the Salesforce skills. Instead it uses the GitHub repo for Salesforce skills , checking the latest published version against the installed version and, if not yet installed locally or an update is available, cloning the repo into a temp directory and installing those. Note that there are significant differences between the original skills bundled with IC and the latest from that repo, so you might want to remove the existing skills before installing the new ones. Of course, if you've customized those skills and/or added your own, you should reconcile carefully to avoid losing anything. When a project is opened — including as part of IDE startup — IC checks for a plugin update. While the IDE already does this for all installed plugins, it only looks for updates that are compatible with the installed JetBrains IDE. Given that IC maintains compatibility with (roughly) one year's worth of JetBrains versions, currently 2025.2-2026.2, users ...

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.5 Issue 2995 - Fixed several issues with ApexDoc Markdown processing during parsing, conversion to HTML, and formatting. Note that the ApexDoc formatter option to add HTML paragraph break elements on blank lines is now automatically disabled if any of the ApexDoc Markdown-related formatter options are enabled. Paragraph breaks are, of course, added in Markdown with two consecutive blank lines, so it didn't make sense to have both options enabled simultaneously. Improved the background threading behavior changes introduced in the previous build to allow immediate cancelation of read-only API calls. This specifically improves the "hand-off" of progress indicators across background threads, and eliminates (or at least minimizes) unnecessary creation of background/worker threads from existing background/worker threads. Added XSD element definitions for FeatureParameter* and GenAiPromptTemplate metadata. Improved progress indicator feedback when refreshing the org met...