Can Forge App Version Be Manually Set or Managed in Marketplace?

Forge
, ,
1

Hi Atlassian Support,

When I deploy a Forge app, a version number (like 2.0.1) is automatically assigned. I couldn’t find any option in the Marketplace listing or Developer Console to configure this manually — for example, to set a version like 1.0.0-rc.

Is this expected behavior?

  • Can version numbers be manually set or tagged in any way?
  • If not, is there a recommended way to communicate app versions to users beyond release notes?

Thanks!

2

Version numbers for Forge apps are set and incremented automatically by the platform - you can’t modify them directly.

Generally, version numbers are an implementation detail and conceptually we want developers and customers to think more about consistently running on the latest version of apps. (For example, see our recent RFC on app version management where we want to move away from a model of discrete versions that customers upgrade to: RFC-106: Future of Forge versioning - Permissions)

So yes, the primary way of communicating changes to customers through the Atlassian platform is using the release notes feature of the Marketplace. The integration between Forge and Marketplace release notes is not ideal because the auto-publish from Forge means that the versions are created and made available to customers before the developer has a chance to specify the details of the release notes. There is an improvement request capturing this limitation here: https://ecosystem.atlassian.net/browse/FRGE-842

However, there’s nothing stopping you building your own release communication mechanism, if you want greater control and flexibility over change communication to customers.

Hope this helps.

3

Thank you for the quick response

4

Yes, versions get assigned automatically by the system after forge deploy - if there are scope changes, and other things causing a major upgrade, there will be major version change, otherwise just a minor, see https://developer.atlassian.com/platform/forge/versions/. (Search this forum for the problems vendors run into with this, eg, RFC-106: Future of Forge versioning - Permissions)

Best,

Eckhard