For example, a Go artifact built for linux/arm should be ignored if we're trying to build the same artifact for darwin/amd64. This might be specific to each plugin, but we should think about whether or not there is a holistic approach that would be better, especially since someone might depend on that artifact from a different (non-Go) plugin (e.g., a bash script that wants to invoke that Go binary). There's very likely some holistic convention to be employed if not a technical control.
For example, a Go artifact built for linux/arm should be ignored if we're trying to build the same artifact for darwin/amd64. This might be specific to each plugin, but we should think about whether or not there is a holistic approach that would be better, especially since someone might depend on that artifact from a different (non-Go) plugin (e.g., a bash script that wants to invoke that Go binary). There's very likely some holistic convention to be employed if not a technical control.