Hi,
I was checking Connect to Forge migration documentation: https://developer.atlassian.com/platform/forge/build-a-connect-on-forge-app/ and there is option to rewrite the app from scratch in Forge: Option A: Re-writing with Forge modules
Looks like you can do a complete rewrite in Forge and reference the Connect app key in manifest file.
app:
id: <the-unique-id-of-your-app>
connect:
key: <your-connect-key>
That is very nice. My question is what happens when you release the new version in the Marketplace?
Will the new version be released as a new version of the same app, or do I need to create a completely new listing?
1 Like
For anyone visiting this thread, yes it seems you can rewrite in Forge and release as a new version of the same Connect app.
Just need to add this in manifest file:
app:
id: <the-unique-id-of-your-app>
connect:
key: <your-connect-key>
Very cool
1 Like
Hii Chhantyal
thanks for your search
If I rewrite my Connect app as a Forge app in the cloud, is it possible to create a new version as a Forge app while using the same App Key in the manifest.yml file, the same key as the one on the Marketplace?
Additionally, if the app contains macros in Confluence, what steps do I need to take to ensure that the macro render remains consistent and the “Error loading the extension!” message does not appear?