If I perform a minor update (in my case connect to forge), and later deploy another update (either a minor or major version), will that deployment override the automatic update behavior — especially in the case of a major version?
In other words, how do manual deployments interact with automatic updates when moving between minor and major versions?
Manual deployments do not override Forge’s versioning behavior. They simply create a new version, and then Forge applies the standard upgrade rules:
Minor versions are automatically rolled out to all sites on the same major version.
Major versions require admin approval and are not automatically applied.
Docs: https://developer.atlassian.com/platform/forge/versions/
If you need to move customers to a newer major version without waiting for individual admin approvals, Forge provides bulk upgrade:
forge bulk-upgrade start --from <major> --to <major>
This lets you programmatically upgrade eligible installations to the newer major version.
Thank you for your response Sir !
So if I have a minor update of connect to forge then I deploy a major update the automatic updating of connect to forge won’t be blocked and requires a manual update right ?
Yes, that’s correct. Let’s take a concrete example with versions:
You release 1.1.0 (minor update)
→ All customers on 1.x.x are automatically upgraded to 1.1.0
Then you release 2.0.0 (major update)
→ Customers on 1.1.0 do not automatically move to 2.0.0
→ They stay on 1.1.0 until an admin approves the major upgrade
If you later release 1.2.0
→ Customers still on major 1.x will automatically move from 1.1.0 → 1.2.0
So a major release (2.0.0) does not block automatic minor updates on the previous major (1.x). It simply creates a new upgrade path that requires manual approval.
If your goal is to move everyone from 1.x to 2.x, you would need to use Forge bulk upgrade.
appreciated so just my specific case is here per example:
1.0 → 1.X → 2.0
will the 1.X rollout keep going even if there is a major in the queue or will it force the major manual update
Otherwise about “If you later release 1.2.0” is it possible to release 2.0 then a 1.2 ?
will the 1.X rollout keep going even if there is a major in the queue or will it force the major manual update
So yes, the 1.X rollout keeps going, even if 2.0.0 exists.
The presence of a major version does not block minor updates on the previous major.
Is it possible to release 2.0 and then later release 1.2?
Yes, absolutely.
You can continue releasing minor versions on the 1.x line even after 2.0.0 exists.
For first point crystal clear thanks !!!
For second point is there a doc or an example for this case I didn’t know about it ^^”
Forge app versioning (major/minor behavior):
https://developer.atlassian.com/platform/forge/versions/
Forge CLI deploy (including --major-version for deploying to a specific major):
https://developer.atlassian.com/platform/forge/cli-reference/deploy/
You mentioned that you are moving from Connect to Forge, in that case, this is critical to understand and review: https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-to-oauth2-scope-equivalences/