I’m working on building a Zapier application using their command line tools and I’ve been experimenting with different builds. During my testing phase, I deployed multiple releases using zapier deploy - specifically versions 2.1.0, 2.1.1, and 2.1.2.
The problem I’m facing is that I want to clean up and remove the older releases (2.1.0 and 2.1.1) so they don’t appear as options in the integration builder interface anymore. I’ve searched through the documentation but can’t locate instructions for this.
What’s strange is when I execute zapier releases, it only displays 2.1.1 and 2.1.2 in the output, yet version 2.1.0 is still visible in the integration builder. I’m not sure why 2.1.0 disappeared from the command output but remains accessible in the web interface.
I attempted to mark version 2.1.1 as deprecated, but there’s a waiting period until August 15th before it becomes effective. I also tried performing a migration from 2.1.1 to 2.1.2, however this didn’t remove the older version from the interface either.
Is there a way to immediately remove these development versions?
yea, that sux! I had the same issue. had to reach out to zapier support too, it’s like they don’t want us deleting stuff! but they helped me out in the end. just gotta be patient with it.
Unfortunately, Zapier doesn’t allow the deletion of deployed versions once they’re live - there isn’t a direct command or interface option for this. The discrepancy between the CLI output and the web interface is expected, as the latter caches version listings differently.
Based on my experience with Zapier apps, starting the deprecation process is the correct approach. While the wait can be frustrating during development, the August 15th date is necessary for existing users to transition their workflows.
In the future, consider maintaining experimental builds in a separate environment or using semantic versioning strategically to avoid similar situations. Once a version is in production, Zapier assumes it may be integrated into live workflows, which explains their deletion safeguards.
Hit this same issue 6 months back while testing webhook configs. Once you deploy versions, Zapier considers them live integrations - even during dev work. The CLI and web interface don’t sync instantly, so that’s why 2.1.0 shows up in the builder but not your command output.
Here’s what saved me: I started using separate dev and production app instances. Test everything on the dev app first, then push clean builds to production. No more version mess.
For your current mess - yeah, deprecation’s your only way out. That waiting period is baked into their system for user protection. Set up proper dev/prod separation now and you won’t deal with this cleanup nightmare again.