Incorrect usage of semver when changing the default version endpoint

[linaori]

The bump from 5.10.0 to 5.11.0 changes the default end-point from 2025-04 to 2025-7, and this is backwards incompatible change, not a new feature or bug fix.

The issue comes from this line:

shopify-api-php/src/Context.php

Line 80 in ed1c9cd

string $apiVersion = ApiVersion::LATEST,

Where this constant value is being updated:

shopify-api-php/src/ApiVersion.php

Line 72 in ed1c9cd

public const LATEST = self::JULY_2025;

When running composer update we should be able to expect no breaking changes when our version constraints do not allow for major versions to be up or downgraded.

[rafaelstz]

Restricting the Shopify SDK version via Composer helps with that.

...
"shopify/shopify-api":"5.10"
...

But for me, it was a surprise to have the latest API used after a Composer update. I believe it can use a global variable or parameter to set the API version, and use the lasted API version as fallback.

[linaori]

I have currently set it to 5.11.* to prevent the same from happening next time, but it would be nicer if it just followed the standards so there won't have to be a next time for anyone.

[lizkenyon]

Hi there 👋

Thank you for the flag!

I agree, with the current functionality you could see breaking changes to the Shopify API on minor versions.

To ensure that we respect semver, we will be removing the LATEST API version constant, and require an explicit API version to be set initializing the library. (Yes, this will be a breaking change and a Major version update.)

Please share if you have any concerns or suggestions around this.