API version in package.xml and sfdx-project.json is still 59 -- override suggested

Hi Scott,

I don’t understand why several weeks after global GA of Spring ‘24 (4 weeks I think), the default API version is still 59. Probably has to do something with dependencies? I couldn’t find a related issue in https://github.com/forcedotcom/cli/issues

Version: @salesforce/cli/2.32.8 win32-x64 node-v20.11.1

As per ~~#2508~~, I do understand that it is “all dictated by the Salesforce CLI. Its templates generally lag the platform releases slightly”.

{
  "packageDirectories": [
    {
      "path": "force-app",
      "default": true
    }
  ],
  "name": "test_api",
  "namespace": "",
  "sfdcLoginUrl": "https://login.salesforce.com",
  "sourceApiVersion": "59.0"
}

As Shane mentions in https://github.com/forcedotcom/cli/issues/2417, “sf project generate does let you specify an --api-version if you don't like the default".

Do you think the choice of (latest) API version could be added to the New Project dialogue, or would that be too complicated?

It seems kind of inconsistent that as from the global GA date, when you publish the respective IC version, new connections are created with the latest API but projects are not.

Also, correct me if I’m wrong, but is the OST created against v59 (the lagging version) if you follow the standard flow? Upon project launch, you’re asked to select a project connection, once you confirm it, OST generation begins. At that time, I haven’t edited sfdx-project.json and package.xml yet, so in order to have the OST created against v60 (the latest version), I would have to cancel the connection selection dialogue, update the files, then select the connection and create the OST?

Thanks in advance.

Comments (4)