is order enforced during

./pants package ::

or

./pants build ::

while I wait for go + protobuf support, I am wondering if it’s possible to use https://www.pantsbuild.org/docs/run-shell-commands target to compile the proto files manually before processing the go build process

What order are you speaking of? The only obvious ordering Pants respects are data dependencies. So if you introduce an

experimental_shell_command

target, properly configure its

outputs

field to capture the generated go files, and then add that target as a manual dependency to the go target that needs to consume the generated files - you have a fighting chance and should give it a whirl since you've then established the data dependency. If you're speaking of the order a

::

glob expands targets to and those targets are consumed by the engine, only the data dependency ordering mentioned can really be relied upon.

ill give it a shot, thanks john