Is there a way to check if running forge deploy would cause a major version update?

Hi,
in our Bitbucket pipeline we want to automatically deploy minor version changes, but require manual approval for major version changes of our Forge app.

Is there any way to find out if a forge deployment would cause a major version update before doing the deployment?
Maybe something like a dry run option for forge cli or some command to specifically check this?

Unfortunately I couldn’t find anything in the forge CLI docs about this, so I’m happy about any hints.

Hi @PatrickvonSteht
I don’t think it’s possible. My usual approach is to deploy to staging first, check for any major or minor version changes, and address them before pushing to production. I once made the mistake of playing around with permissions to find the right scope and forgot about it in development. But when I saw the major version update in staging, I was able to catch it and fix the permissions before deploying to production.

1 Like

I don’t think it’s currently possible, but would like to have something like a parameter to prevent / allow major updates when pushing a version

I found out that RFC-71 contains the idea for “Preflight Update Checks”, which address this issue. So it’s not there yet, but will be: RFC-71: Improving Connect to Forge and Forge Platform Upgrades

2 Likes

Indeed, it is also going to help app developers detect any changes that lead to loss of Runs on Atlassian eligibility. This change would be added to the Forge roadmap soon.

Cheers,

Agi

1 Like