shuangkun tian

Now released in 3.5.3， you can test it.

> I believe that supporting version control for workflows and templates is crucial, rather than directly updating existing objects, which can be a risky operation. The update action should still...

After reproducing it, there are indeed some problems and need to think about how to fix it.

Does the first executingWorkflowMetadata!=nil should be workflowMetadata? @gnadaban

It is because node `tails` was set skipped when evaluate false, it is a type of fullfiled, which cause post-tails running.

You can use heads.Succeeded/tails.Succeeded instead of heads/tails. Because `depends: task` is equivalent to `depends: (task.Succeeded || task.Skipped || task.Daemoned)`. @gisjedi ```yaml templates: - name: main dag: tasks: - name: flip-coin...

> > * [ ] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application > > > * @agilgur5 > >...

> @shuangkun Please update the list of sponsors in the issue description. ok, I have.

> So, it sounds like previously the execution of a Workflow was allowed to continue even if the previous Step's Outputs weren't reconciled? Are you essentially preventing the next Step...

Yes, I think this was the case before, although under normal circumstances output will be processed before pod status normally, because this resource is indeed created earlier. But on a...