Understanding minor version updates and automatic upgrades

[scottohara]

We have just completed our first adoption of Forge manifest for one of apps (Connect-on-Forge).

Reading through Minor version updates (Connect to Forge) and the associated Changelog entry, we believe that we satisfy the eligibility criteria for a “minor version update”. Specifically:

Scopes

Our Connect-on-Forge app inherits the same scopes as our Connect app.

The manifest was created using the @atlassian/connect-to-forge tool, which converted these scopes from our atlassian-connect.json descriptor:

"scopes": ["READ", "WRITE", "DELETE"],

…into these permissions:

permissions:
  scopes:
    - read:connect-jira
    - write:connect-jira
    - delete:connect-jira

BaseUrl

The baseUrlin atlassian-connect.json and remotes[].baseUrl in manifest.yml for our Connect-on-Forge app are identical.

There are no other remotes besides our Connect one.

Licensing

Both the previous Connect-only version and the new Connect-on-Forge version have licensing: enabled (it is a paid Marketplace app)

Based on the above, we think that our adoption of Forge should be considered a minor version update.

Versioning

We followed the guides for How to adopt Forge from Connect and https://developer.atlassian.com/platform/adopting-forge-from-connect/listing-your-app-on-marketplace/ , and tested that our Connect-on-Forge version correctly replaces the previous Connect-only version when installed into our dev & staging environments/instances.

Our understanding is that all Forge apps start life at version 1.1.0 (after invoking forge register), and first deployment to the development environment is typically 2.0.0.

When we completed step 4 of the above “Listing your Forge successor app” guide, which is to publish a new app version in the Marketplace by selecting our Forge app, the new Marketplace version was therefore 2.0.0. Our previous Connect-only version was 1.x.

In typical SemVer parlance, 1.x → 2.x looks to us like a major version bump, and certainly our newly published app version had to undergo app review (and was subsequently approved; even though there are zero differences in this app version from the previous one….but we’re assuming that every Forge app has to be re-reviewed, even Connect apps adopting Forge).

So far, it has only been about 20 hours since the new app version was approved, and we understand that rollouts happen over a 120 hour (5 day) period, so we’re certainly not too concerned at this stage that our developer console still lists zero installs of our production Connect-on-Forge app.

But while we wait, we just wanted to confirm our understanding that when the above documentation refers to “Minor version updates” and lists the criteria for what is considered a minor version, does it matter that our first published Forge version is 2.x and our last Connect version was 1.x?

Are we still eligible for admin approval-less rollout, or do we need to consider looking into forge bulk-upgrade?

[FeiyangYe]

Hi @scottohara ,

Congratulations on your first Forge adoption! Based on the information you provided above, your Connect-on-Forge app should be eligible for automatic minor version update. However, we have temporarily paused this feature (more details on this change log) and the team is actively working on some improvements on the robustness. We will re-enable the feature once these improvements are complete.

Thank you for your patience and hope that helps.

[remie]

Hi @FeiyangYe ,

Can you clarify if this means that @scottohara ‘s app will not be automatically updated in the customer instances and that this means that all their customers will need to manually update to the new Forge version they released?

Kind regards,

Remie Bolte

[YasuhiroKawamura]

Hi @FeiyangYe,

Do you have any timeline or estimate for when the minor version update rollout will be re-enabled?

Best regards,
Yasuhiro

[FeiyangYe]

Hi @remie, that’s correct. Until the automatic minor version update is re-enabled, the customers will need to manually update from Connect to the new Forge version.

[KhaNguyen2]

Our app was also approved yesterday and was eligible for minor version update. But it got stuck at ~5 installations so far after 12+ hours.

Do we have a timeline for automatic rollout to come back? In the meantime, is there any alternative to make our customer upgrade the app?

[rmassaioli]

I can say that we have a team actively working on this. We will be looking to put out a conservative estimate for bringing this feature back very soon: that estimate will, ideally, come out tomorrow.

[nathanwaters]

If the app gets stuck behind a manual update wall, that’s it, dead app, no coming back. Atlassian continues to be ignorant and uncaring to this death spiral. Unrealistic migration deadlines ticking away while RFC-106: Future of Forge versioning - Permissions is nowhere near being ready for developers to use.

[rmassaioli]

An update had been posted to https://jira.atlassian.com/browse/ECO-1077, we will communicate there for all future updates.

[scottohara]

For anyone that hasn’t clicked through to that linked response above, allow me to spoil the ending for you:

With conservative estimates of the remaining work, we aim to re-enable seamless updates by 17th of November 2025.

Over a month before we get seamless updates, and the countdown to Connect financial penalties marches on…

What a joke.