Issue Summary

When a Forge successor (migrated from connect-to-forge) app is published, two versions of the app are created. Unexpectedly, one of these versions is listed as private. The approval request is sent for the lower version, while the higher version remains privately listed. When installing the app from the marketplace, the privately listed version gets installed, causing confusion.

How is this bug impacting the rollout?

1. When publishing a Forge successor app (migrated from Connect to Forge), two versions are created in the Marketplace. The lower version (e.g., v2.0.0) is submitted for approval, while the higher version (e.g., v2.1.0) remains private.

2. Due to this bug, the private higher version (v2.1.0) is being rolled out to both existing and new customers instead of the intended public version (v2.0.0). This means customers are receiving a private, unapproved version of the app.

3. The current workaround is to manually update the higher version's visibility to public in the Marketplace.

Steps to Reproduce

1. Click ‘Create version’
2. Click ‘Forge app’
3. Click through the version details as required
4. Click to ‘Make public’.
5. Wait for the automatic process to complete
6. After, there is a pending version of the app(Ex: 1.3.0), and a private(Ex: 1.4.0) version

Expected Results

Only one version of app should be published and the version should be marked private

Actual Results

Two versions of the app are created

Workaround

Manually make the app version public