Staggered reintroduction of minor version updates for Connect to Forge apps with over 50,000 users
- Announced
- APIs
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3320
From 2026-07-08, we will begin removing the temporary restriction announced in CHANGE-3109 that required every update to Connect to Forge apps with over 50,000 users to be classified as a major version update. We will contact partners first before lifting the restriction on their app(s).
This restriction was introduced as a temporary safety measure to protect downstream Forge services from sudden traffic spikes during large version migrations. Since then, we have completed significant scaling and reliability work across the affected services, so we are now able to return these apps to the normal minor version update path.
What is changing
- Affected Forge apps can return to using minor version updates, rather than being forced into major version updates and
forge version bulk-upgradebatches. - You will still be able to use
forge version bulk-upgradeif you prefer a controlled, batched rollout - this remains available and unchanged.
For detailed information on how to use forge version bulk-upgrade, see https://developer.atlassian.com/platform/forge/cli-reference/version-bulk-upgrade/.
How are we rolling this out
To avoid any unexpected impact on in-flight migration activities, we will not automatically re-enable minor version updates for every affected app at once. Instead:
- We will contact affected partners individually to confirm whether you would like minor version updates re-enabled for your app, and to coordinate timing against your current migration plans.
- If you would like the restriction removed for your app now, please reach out to Ecosystem Support, and we will action the request.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.