CI: host job doesn't depend on success of custom build jobs

[connec]

It's not clear if this is intentional behaviour or not, but the condition for the host GitHub Actions job does not depend on the outcome of any custom build jobs:

cargo-dist/cargo-dist/templates/ci/github_ci.yml.j2

Lines 392 to 394 in 5e7826f

	if: ${{ always() && needs.plan.outputs.publishing == 'true' && (needs.build-global-artifacts.result == 'skipped' || needs.build-global-artifacts.result == 'success')
	{{%- if build_local_artifacts %}} && (needs.build-local-artifacts.result == 'skipped' || needs.build-local-artifacts.result == 'success') {{%- endif %}}
	{{{- " }}" | safe }}}

[Gankra]

That does indeed seem not-quite-right. I know this condition has gone through a lot of evolution, and has some really specific subtleties around the publish-a-library-which-skips-the-build-steps-but-still-runs-later-steps usecase.

This condition also used to have to handle the global step not existing, but we kinda-recently made changes that made the global step always appear in the graph.

...all that said I think it is accurate to say this should be considering custom local and global build jobs.