Still on v59 in package.xml and sfdx-project.json

[René Görgens]

Hi Scott,

Today I created a fresh SFDX project and found that the API version is still 59.0 in:

• package.xml
• sfdx-project.json

The API version configured on the project connection is 60.0.

The issue is reproducible.

As a sidenote, I’m still getting the below error against a vanilla developer org but NOT against a partner developer org

• With all API settings on 60.0

“Failed to load standard Apex types using the Salesforce Tooling REST API. Using bundled standard Apex types instead. Note that the generated offline symbol table may not accurately reflect the organization's enabled optional features.”

[Scott Wells]

That's all dictated by the Salesforce CLI. Its templates generally lag the platform releases slightly. Once it is properly updated to default to API v60.0, new projects should be initialized with that version.

IC2's Inconsistent API version code inspection should help identify such disparities, though, if configured to use the configured connection API version as the reference point.

[Scott Wells]

Combination of the API version in the files for a new CLI-created project coming from the CLI and the Inconsistent API version code inspection already identifying and assisting with API version alignment.

[René Görgens]

Thanks for reminding me, I once knew about this lag but forgot.
Indeed the code inspection highlights these issues and makes it easy to fix them.