Processes defined by empty string are broken (again!)

A constraint has been added that requires an item in processes to not be an empty string. However, the Laravel configuration depends on this:

It runs /init if no command is specified. Otherwise it runs the specified command.

1 Like

Btw, I said “again” because this update was also made in September:

This update also makes this example not work anymore:

I know the fix is simple, but it sucks a LOT to see a bunch of apps suddenly fail to deploy. Especially because it happened a few months ago as well.

Sorry about that. We just deployed a fix - can you try again?

Going to try another app, but it worked fine on the first one I tried. Thanks!

Yep, tried on two apps now. Seems fine, thank you!