Protected Workflow - Merging PR automatically publishes workflow

đź’¬ Workflows
, ,
1

For a protected workflow, it’s my understanding that merging a change to main no longer automatically creates and publishes a new version of the workflow (based on this announcement and this doc). However, I still think this is happening automatically, for me at least,

  1. From main, I look at workflow versions, I see 2.0.0 (latest) and it’s live.
  2. I create branch, make change, commit change and create PR.
  3. I merge PR to main.
  4. I go grab coffee.
  5. From main, I look at workflow versions, I see 3.0.0 (latest) and it’s live. However, I did not create a 3.0.0 version, and I did not publish anything.

Any idea why this is happening?

1 Like
3

Hey @lkiss,

Can you confirm whether you're seeing this issue in Self-Hosted or Cloud?
It also helps to double-check your Retool version, since this update is already available on Cloud (latest) and in edge versions 3.307+.

In my case, I'm using Self-Hosted Retool, and the update isn’t available yet because my version is 3.284.1. So depending on your setup, the feature might simply not have rolled out to your environment yet.

If you can share your version number, Retool Team can help confirm whether this update should be visible for you or if you may need to upgrade.

4

Good callout – We’re using cloud.

1 Like
5

Hey @lkiss - good catch. It looks like that particular feature was never fully rolled out, but I can certainly enable it for your org if you'd like!

1 Like
6

That would be great. Thank you.

2 Likes
7

Done! Let me know once you've had a chance to test it out. :+1:

1 Like
8

Tested. Works perfectly. Thanks @Darren

2 Likes