2.4.1.9 release notes

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-stubbed interfaces for the LWC state management APIs. The documentation for these isn't great, at least in terms of the exact interfaces, but hopefully what I've provided here is quite decent. I'm certainly open to suggestions for improvement and of course fixes if there are still issues or inaccuracies.
  • Issue 3013 - Added a few missing properties in the LWC record API module types.
  • Issue 3014 - Fixed an issue with LWC TypeScript files that import HTML and CSS files.
  • Fixed a few issues with Flow diagrams in 2026.2+/Mermaid 11+:
    • Restored diagram node icons.
    • Removed the diagram configuration option to use the Elk renderer since it doesn't seem to be supported (or at least have any effect) in Mermaid 11+.
  • Improved UI bundle creation error handling and reporting.
  • Improved the way that IC helps install the plugin update when a new version is detected. Previously when a new version was found, the Settings | Plugins dialog would be displayed focused on the IC2 plugin. However, it looks like there's no guarantee that the IDE will have updated its plugin repository version information by the time that dialog is displayed, so IC now explicitly triggers the IDE's Check for Updates action to force an update notification (assuming that the local machine allows the IDE to communicate with the JetBrains plugin repository).
  • Many other internal improvements to strengthen the foundation for subsequent work. I've tested these changes extensively, but if you do find any issues or regressions, please let me know and I'll address them ASAP.

Note that support for 2025.2 JetBrains IDEs will be removed soon. Please make sure that you're using 2025.3+ for the best experience going forward.