Illuminated Cloud Announcements

2.4.0.0 Issue 2939  - Fixed an issue that could occur when an error is reported for a source file by the API or CLI with a simplified path, e.g.,  classes/Foo.cls , where the local path is more complex, e.g.,  classes/subfolder/Foo.cls . Now if no matches are found using the reported path, IC looks for a unique source file with the same name and, if found, reports against it. Issue 2941  - As of  2026.1 , IntelliJ IDEA includes  first-class language support  for JavaScript, TypeScript, and CSS  for free  (i.e., without an Ultimate subscription). This includes not just basic language support features like intelligent code completion, reference navigation, source code formatting, etc., but also extensive refactorings, static code analysis including integration of ESLint and Stylelint, tight npm integration, and much more. The main things that are notably missing are the JavaScript debugger and Jest support, but I'm working on a very tight integ...

2.3.9.9 Enabled support for the 2026.1 JetBrains IDEs that are now in a  release candidate state . As always, if you see issues with a pre-release IDE build, please revert to the most recent released build and let me know about the issues you've seen so that I can address them. Issue 2929  - Made sure that the connection icon includes a lock overlay consistently for connections that require write confirmation. It was most noticeably missing in the connection status bar widget. Issue 2936  - Fixed a  StackOverflowError  that could occur when overriding dynamic file types. Fixed a few issues with placeholder  *.object-meta.xml  files being incorrectly treated as full custom object files during metadata deployment and retrieval. Improved CLI-based deployment result reporting where some information was being sent to  successes  and  failures  instead of  files  in the JSON result. Added support for contextually-correct code co...

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.9.7 NOTE:  In the next few months, Atlassian will be  sunsetting  the Bitbucket Cloud issue tracker and wiki features. As a result, I will be migrating the IC  public issue tracker  and  user guide  content into GitHub (using this as a long overdue opportunity to refresh the user guide as I do so). As much as possible, I would like to retain user associations in the migrated issues. If you have logged or commented on issues in the IC public issue tracker and would like to have your migrated issues and comments attributed to your GitHub username, please send both your Bitbucket name and GitHub username via  email  so that I can include them in the mappings used by the issue migration script. No worries if you'd prefer not to provide that information. All other issues and comments will be attributed either to me or to an anonymous/unspecified user, and I will try to include the original Bitbucket username in the issue summary or comment tex...

2.3.9.6 Issue 2922  (partial) - Implemented a few more fixes for  PsiInvalidElementAccessException  instances that I observed in my own work. I'll continue to try to track down the root cause of these invalid elements, but minimally I'm trying to be defensive against their presence and allow for recovery when possible. Issue 2925  - Corrected the data type of  ConnectApi.CdpQueryOutputV2.metadata . Note that the OST must be regenerated to see the effects of this change. Issue 2926  - Made IC's file type overriders — used for metadata files with a single extension but multiple MIME types, e.g., static resources, content assets, email templates, and documents — much more selective about files for which they try to determine a file type. All files must pass the following gates: Must be under a configured, deployable source root. Resource roots are  not  considered source roots for this check. Must be in an IC module/project. Additionally the file typ...

2.3.9.5 Issue 2918  - Added the  namespace  value from  sfdx-project.json  as a read-only field in the scratch org creation dialog when creating in the context of a source format project with a populated  namespace  value. Note that with this change, the  No Namespace  checkbox is only visible when a namespace is present in  sfdx-project.json , and enabling that option also hides the  Namespace  field (and vice-versa). Issue 2919  - Fixed an issue that could occur when renaming Apex classes/triggers via the file rather than the class/trigger name where non-Apex references to that name, e.g., in a  package.xml  file, would be incorrectly updated with the file name instead of the class/trigger name. Issue 2922  (partial) - Protected against a potential invalid element access exception when trying to find the module for a cache dependency. Unfortunately this is still a downstream behavior of the original invali...

2.3.9.4 Issue 2907  - Spring '26 / API v66.0 update Updated the SOAP client for API v66.0. Updated the API version used for primary communication with Salesforce APIs to 66.0. Added 66.0 as an available API version number for configured connections. Updated  metadata.xsd  based on the API v66.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Spring '26. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v66.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Spring '26 changes. Note that I have not yet reconciled IC's own LWC TypeScript definitions with the latest from  @salesforce/lightning-types  but I do plan to do that shortly. If you're running into issues with some incompatibility between the two, please let me know about the specific instance(s) and I'll fast-track those. Updated the bundled SLDS CSS and SVG...