Adopting Forge from Connect is now Generally Available

Forge Adopting Forge from Connect
, ,
1

Hi everyone,

Last month, we announced that Adopting Forge from Connect is generally available. This signals that the migration pathway has been tested and proven operationally ready, and that the process is available for all partners.

We’ve also published a blog which announces that all new platform extensibility features will only be available through Forge. Consolidating on one platform accelerates delivery of new features (such as Rovo), allowing Atlassian and our partners to build once, adopt everywhere, with the latest Atlassian Cloud capabilities. The blog also explores some of the experiences from partners who have been through the process of adopting Forge and publishing their apps on the marketplace.

Looking forward, we’re committed to continuing to improve the experience, making it easier for partners to bring their apps to Forge. We recently published an RFC exploring how Data Residency may work for Forge Remote apps, delivering the capability for Connect apps utilising Data Residency to move to Forge. We also plan to publish an RFC which explores major and minor updates in the coming week/s.

3 Likes
2

What does this do in normal language without all the corporate fluff?

Partners are being forced to “adopt” Forge by FY26 or they lose their current marketplace badge. It’s very cruel to force adoption while the platform is immature and Forge pricing is still uncertain.

For partners backed into this corner, does it mean this is now possible?

  1. Convert descriptor to manifest
  2. Make no other code/hosting changes whatsoever
  3. Connect app is now considered a Forge app
2 Likes
3

Hey @nathanwaters,

The FAQ on that linked page provides a description of what qualifies as a Forge app.

With regards to this announcement, all Connect capabilities (aside from Data Residency) should work when a Connect app (with all or some of its modules) is migrated to Forge.

While Data Residency is not yet supported, apps which leverage that capability are able to test adopting Forge from Connect today, however they will have to retain only their baseUrl for the moment. Once Data Residency for Forge Remotes is available, those apps would be able to move their entire Connect app into Forge.

4

Ok yep so descriptor to manifest conversion makes it considered a Forge app. You might want to have a word with that partnerships team.

Progressive adoption is a cool idea. It probably would have been a far cleaner execution strategy to begin Forge that way instead of building a separate parallel platform.

If developers see the benefit they’ll voluntarily adopt the new features.

But forcing adoption is only going to backfire and anger the ecosystem further.

5

This topic was automatically closed after 30 days. New replies are no longer allowed.