How does Forge app versioning work?

Forge
1

I noticed that the Forge apps that I have installed in my development site (listed under Jira settings > Apps > Manage apps) have version numbers of at least 2.x. Where do these version numbers come from and when/how are they updated?

It looks like new apps that are deployed for the production environment using the Forge CLI always start at version 2.1.0. I would have expected that the version number starts at 1.0.0.

1 Like
2

Hi @klaussner,

Not an answer to your question, but you might want to look at this topic where there has been some discussion around this already.

If you can’t access that topic, apply for access to Marketplace Partner topics here.

Cheers,
Sven

2 Likes
3

Thanks, Sven! That topic was very helpful.

A short summary in case someone else is looking for it:

  • The smallest possible production version number is 2.0.0 because of internal handling of version numbers.
  • Changes in the manifest that require customer approval (e.g., scope changes, licensing changes, new egress permissions) bump the major version number.
  • All other deployments bump the minor version number (it looks like the third component is ignored).
6 Likes
Getting error while publishing forge app create on Jira product
4

Both links posted by @anon87782987 are apparently dead, but…

Are these version numbers accessible from Bitbucket pipelines, so that it’d be simple to tag a given set of deployed code with a given Forge-generated version number (for example)?

5

The first link is still available, though in a Marketplace Partner only section - you can apply to access these sections here (replaces the second and indeed dead link):

2 Likes
6

As for the version numbers, they are in principle accessible via the Marketplace REST API, and also via the newer Atlassian GraphQL API (don’t have any code or specific pointers handy right now).

2 Likes