Hi @Nagamanickam 

Seems like this should be posted in the Developer Zone: https://community.zapier.com/p/developer-zone

Hey @Nagamanickam, great question!

As long as you do NOT migrate users to the new version, their Zaps will remain on the current version. 

Assuming the app is public, you can still promote the new version to make it the default version for new Zaps and steps. Promotion alone will not update existing Zaps. 

Here’s a handy resource with links to more context on promotion vs. migration:

https://platform.zapier.com/manage/versions

HI Everyone,

I found the following topic in the Zapier documentation. I have a question regarding this.

In my case, I fixed a bug. This will affect the existing zap because I made a change to the returning payload. I want to release this without causing any issues to the existing system. So, should I use 'Major' or 'patch'?

Please tag this to right team who can answer .

Thanks in Advance

Hi @Nagamanickam,

Whether this change should be considered a patch or a major/minor change is largely up to you and your preferences. 

From your description, however, it sounds like this might be a breaking change, blocking migration, correct?

If so, that would most conventionally fit the “Major” description.

These resources might offer some insights on the scope of your change:

• Change output field key
• Change output data response

If you’d like further assistance, or help digging into the exact change’s impact, please feel free to reach out to the Platform Support team: https://developer.zapier.com/contact

They’ll be able to discuss the change in more detail and help determine if it’s a breaking change or not.