Illuminated Cloud Announcements

2.3.8.1 Issue 2858  - Winter '26 / API v65.0 update additional items Updated the SOAP client for API v65.0. Updated  metadata.xsd  based on the API v65.0 Metadata API SOAP WSDL. Added stub definitions for the  LWC state management API . These are  very  simple stubs that will be expanded into complete signature definitions once the APIs are better documented. Issue 2871  - The prospective fix for duplicate path segments in metadata files retrieved via the Salesforce CLI from  2.3.8.0  had issues, so this build includes what I'm hoping is a more complete and reliable workaround/fix.

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.9 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  OAuth connections  to ensure seamless continued support. Implemented a workaround for a Salesforce CLI issue that could result in the paths of newly-retrieved metadat...

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.7.7 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. Updated all integrated API documentation. The Apex  Annot...

2.3.7.6 Issue 2851  - Fixed a possible infinite loop that could occur when traversing circular Flow node references. Issue 2856  - Minimized some read actions to try to address yet another reported "IC might be slowing things down". As always, if you continue to see these types of reports, please send over the corresponding thread dumps and I'll try to take care of them. Issue 2859  - Added full support for Salesforce's  ApexDoc specification . All enhancements in that spec are available regardless of whether or not the user wishes to ensure compliance with the spec. If the user does wish to ensure compliance, a new  Strict mode  ApexDoc validator inspection option is now available that flags usages of unsupported tags and macros as errors and disables Markdown-based text formatting. Note that users of  IcApexDoc  should also make sure to update to version  1.0.1.3  to ensure parity support for the Salesforce ApexDoc spec.  

2.3.7.5 Issue 2847  - Prospective fix for an issue observed in user-provided log extracts where IC is attempting to cache a namespace for an invalid, non-null element. This could well be a downstream side-effect of an another issue. If so, I'll continue to work with the reporting users to find and fix the ultimate root cause. Issue 2848  - Added a new tab-level option to the SOQL Query tool window to disable query validation specifically for that tab. This is useful when a query would be flagged by certain validations, e.g., as having unconstrained sub-queries, but the user knows that the query will execute without issue. It allows validation to be disabled for exactly those queries while remaining enabled in general. Validation can be enabled/disabled via a toolbar toggle button and via a checkbox in all of the actual validation dialogs. Issue 2849  - Added aggressive caching of node IDs in the build options dialog as a prospective fix for yet another "Illuminated Cloud ...