Legacy API versions remain after upgrading

[sjames-hms]

My org was originally using a legacy version of FormulaShare and in our sandbox, I recently upgraded to version 3.27. However, the following class and test class: [fflib_InOrder] and [fflib_InOrderTest] have an API version of 30. We are trying to confirm that all of the legacy API versions from 21.0 to 30.0 are removed from our org. Is there another upgrade of FormulaShare we should be using? Thank you.

[LawrenceLoz]

Hi @sjames-hms many thanks for flagging this.

3.27 is the latest version of the FormulaShare managed package, though the class you mention and several others from the fflib libraries we use in the app are on some quite old API versions.

These are kept up to date in the project but it appears there's been an issue with the version updates for libraries getting through to our packaging org. We'll certainly resolve this in our Winter release which we're aiming to distribute for use in production around December/January and ensure all classes are on recent versions.

If the work you're doing to remove legacy API versions relates to the upcoming retirement of versions 21.0 to 30.0 it's worth noting this doesn't directly affect versioned metadata components within a package (https://help.salesforce.com/s/articleView?id=000389618&type=1).

I can appreciate from a governance perspective though you may need to ensure outdated API versions aren't used across the board. Let me know if it waiting until December/January would be an issue for you - we'd be happy to fast-track a new package version with the API version updates in place if needed.

I'll keep this issue open until this is resolved in any case

[sjames-hms]

Yes, we can wait until Dec/Jan for the updated package. Thank you for responding back so quickly.