This was missed on the previous fix. It now references the correct artifact name now that this is back to running as part of the build workflow. Blame: 181f0f1806
181f0f1806