Issue Summary:

For Forge apps, the build number of previously backported versions might be higher than the latest major version, which will disable the update button for customers not running the latest major release. 

Steps to Reproduce

1. Create a Forge app and release it in the Marketplace.
2. Update the app manifest in a way that a new release is considered a major version. 
3. Release the new version in the Marketplace. 
4. Now, revert the change in the manifest and release a minor version for the previous major version. 

   forge deploy --major-version [version] 

Expected Results

The new version received a build number that list it alongside its major releases. 

Actual Results

The new version build number might not update properly, which will put it above the latest major version. 

Workaround

Whenever a backported update is released, also release a new version of your latest major version. 

This will keep the update button available, since the latest major version will always appear at the top of the list.