I have been doing a lot of deployment to the development environment while working on my Forge app. I’m getting ready to deploy to production, but I don’t want the version to be so high. Is there anything I can do about that?
Each environment has their own versioning, so any version on development, staging or a custom environment will not reflect the versioning on production.
Basically, Forge versioning increments per environment, and will either be a major or minor version based on whether or not there are “breaking” changes that require manual approval.
However, I would say, as a former Release Manager, that Forge versioning is absolutely bonkers. I would not spent too many brain cycles on it trying to either understand it or worry about it.
3 Likes
+1 to what @remie said, your versions increment per environment deployment.
So for example, I have an app in development on version 4.3.0 and after deploying it to staging for the first time, the staging version is now 2.0.0.
You can read more about how forge automatically handles versioning at https://developer.atlassian.com/platform/forge/versions/
1 Like
@mpaisley can you please shed some light as to why Forge skips 1.0.0?
This entire process is confusing. Now I want to share the app with a coworker to have them look at it before it goes onto the Marketplace. I can’t seem to generate a sharing link, I guess because I already enabled licensing in the manifest. I tried redeploying with licensing turned off but it didn’t allow me to generate a link. It seems strange that I would have to make a copy of my project just to do a pre-deploy test installation. Can I delete the app from the developer console, re-register and treat it as a new app?
Can I delete the app from the developer console, re-register and treat it as a new app?
Yes, you can - I usually remove the existing app id from my manifest then use ‘forge register’ and it’ll assign a new App ID which will treat it like a new app.