2.3.1.9 release notes

2.3.1.9

  • Issue 2584 - Summer '24 / API v61.0 updates
    • Updated all SOAP API clients to be based on the API v61.0 WSDLs.
    • Updated the API version used for primary communication with Salesforce APIs to 61.0.
    • Added 61.0 as an available API version number for configured connections.
    • Updated the OST version number to prompt regeneration for system API changes in API v60.0.
    • Updated the bundled completions?type=apex Tooling REST API response to be based on the API v61.0 REST endpoint.
    • Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '24 changes.
    • Updated the bundled SLDS CSS and SVG icons to 2.24.2.
    • Updated for new org features, standard value set names, metadata XML file type extensions, etc.
    • Updated all integrated API documentation.
    • Added full support for the new Apex @InvocableVariable annotation DefaultValue and PlaceholderText attributes. I've also updated the Apex Annotation and Modifier Agreement code inspection to flag invalid usages of those attributes, but I've currently disabled the logic to flag DefaultValue values that are not assignable to the annotated field's declared data type as I'm seeing quite a few issues with that attribute during deployment. I've reached out to Salesforce to see if those are known issues that need to be fixed or an incorrect understanding on my part. Once things work as expected (or at least as intended), I'll restore that logic to an active state with any necessary changes.
    • Added SOQL language string literal injection for the query argument of System.Database.getCursor*() methods.
    • Generalized support for up to four levels of nested SOQL queries in Apex. This was already supported for standalone SOQL queries, but embedded SOQL queries were flagged as invalid previously as they weren't supported. Now both usages support four levels of nesting, i.e., five total levels including the top-level query.
  • Fixed an issue that could result in Apex types being absent from the Navigate | Type action.