Rename activation artifact to avoid invalid-name upload failure#54117
Conversation
…ame upload failure Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
PR TriageCategory: bug | Risk: medium | Priority: medium (score 40/100)
|
PR TriageCategory: Duplicate of #54146 addressing the same activation-artifact naming bug. Recommend closing in favor of #54146 once verified; diff is mostly regenerated lock.yml noise. Automated triage — see the [triage report issue] for full context.
|
The
activationjob's artifact upload was failing across the entire smoke-test fleet withCreate Artifact Container failed: The artifact name activation is not valid.GitHub's Actions artifact API rejects the bare single-word nameactivation, causing the upload step to fail before theagentjob even starts.Changes
constants.ActivationArtifactNamechanged from"activation"to"aw-activation"inpkg/constants/job_constants.go. Theactivationjob name itself (ActivationJobName) is untouched — only the physical artifact name changed..lock.ymlfiles under.github/workflows/andpkg/cli/workflows/regenerated so upload/download-artifact steps reference the new name."activation"literals withconstants.ActivationArtifactNamein artifact-set resolution/filter tests and threat-detection step tests; regenerated wasm golden fixtures.