method for running tasks in series

[jdx]

I've been trying to avoid having the capability of defining task dependencies in series as an explicit feature just to keep things simple since it's trivially done just by calling mise run inside of a task:

[tasks.build]
run = ['mise run a', 'mise run b', 'mise run c']

however, because of several reasons (which I can explain if people are curious but I don't think it matters all that much), this just isn't good enough. I think we may need a way to explicitly define dependencies should run in series. I think users will like this because mise run I've often thought users see as a bit of a kluge even though it works fine. How do you think this could look in mise.toml? I think I only have terrible ideas:

[tasks.build]
depends_series = ['a', 'b', 'c']

[tasks.build]
depends = ['a', '+', 'b', '+', 'c']

I'm not 100% sure I would actually implement this. The drawbacks of not having this are not things we can't live with. Part of the issue is coming up with good syntax but the other is the complexity in the codebase this would add (which I'm not too sure about right now). Also the complexity of just having more features to document and explain to people how to use is a cost I'm weighing. Still, good syntax is definitely a blocker for starting it.

[EricDriussi]

Personally, I don't really have a use case for explicitly running tasks in series.
What I would say is that using mise run seems in general counter intuitive, since there is specific syntax to handle deps. Plus, it gets messy when tasks get more complex.

A fair example of this is, with all respect, this very project's tasks.toml, IMO.
I was trying to understand the docker setup and got lost at the second mise run. Maybe I'm just grug brained but I'm guessing more people also are.

Regarding semantics, I would expect this feature to exist for depends_post as well, so having a depends_series would maybe also introduce depends_post_series, for a total of 4 properties to handle dependencies.
Maybe an inline table is in order at that point? Something like:

depends = { pre = { sync = ["a"], async = ["b"] }, post = { sync = ["c"], async = ["d"] } }

Or maybe a mix of full and inline tables?

[tasks.build.depends]
pre = { sync = ["a"], async = ["b"] }
post = { sync = ["c"], async = ["d"] }

Breaking changes suck but the old syntax could be preserved quietly for current users, while documenting the new one for new ones.
Just some thoughts!