Thanks Shane. That explains why I couldn’t find any instructions.
Given that my workflow bundle contains an embedded script file in the resources folder, I was expecting that notarization would be required. Hopefully this means I won’t get any macOS Gatekeeper issues from users.
I assume there’s still value in code signing the workflow bundle?
If I understand correctly, converting a .workflow into an .app (in Automator) creates a bundle with a file named “Automator Application Stub” which is a Unix executable, which I assume is why the .app requires notarization?
The same goes for Script Editor which creates .app bundles with the Unix executable “applet”.