Skip to content

Rename activation artifact to avoid invalid-name upload failure - #54117

Draft
pelikhan with Copilot wants to merge 2 commits into
mainfrom
copilot/aw-failures-fix-artifact-name-validation
Draft

Rename activation artifact to avoid invalid-name upload failure#54117
pelikhan with Copilot wants to merge 2 commits into
mainfrom
copilot/aw-failures-fix-artifact-name-validation

Conversation

Copilot AI commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

The activation job's artifact upload was failing across the entire smoke-test fleet with Create Artifact Container failed: The artifact name activation is not valid. GitHub's Actions artifact API rejects the bare single-word name activation, causing the upload step to fail before the agent job even starts.

Changes

  • Renamed artifact constant: constants.ActivationArtifactName changed from "activation" to "aw-activation" in pkg/constants/job_constants.go. The activation job name itself (ActivationJobName) is untouched — only the physical artifact name changed.
  • Recompiled generated workflows: all .lock.yml files under .github/workflows/ and pkg/cli/workflows/ regenerated so upload/download-artifact steps reference the new name.
  • Updated tests: replaced hardcoded "activation" literals with constants.ActivationArtifactName in artifact-set resolution/filter tests and threat-detection step tests; regenerated wasm golden fixtures.
// Before
const ActivationArtifactName = "activation"

// After
const ActivationArtifactName = "aw-activation"

…ame upload failure

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix artifact upload failure for activation job Rename activation artifact to avoid invalid-name upload failure Aug 20, 2026
Copilot AI requested a review from pelikhan August 20, 2026 02:14
@github-actions

Copy link
Copy Markdown
Contributor

PR Triage

Category: bug | Risk: medium | Priority: medium (score 40/100)
Score breakdown: impact 20 + urgency 12 + quality 8
Recommended action: defer
Fixes the same activation-artifact naming failure as #54146, but with a much larger 1757-line/300-file diff. Recommend deferring/closing in favor of #54146 unless this PR carries additional necessary fixes.

Generated by 🔧 PR Triage Agent · auto · 62.9 AIC · ⌖ 7.05 AIC · ⊞ 8.3K ·

@github-actions

Copy link
Copy Markdown
Contributor

PR Triage

Category: bug · Risk: medium · Score: 33/100 · Action: close

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.

Generated by 🔧 PR Triage Agent · auto · 67 AIC · ⌖ 10.2 AIC · ⊞ 8.3K ·

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[aw-failures] [P0] Artifact upload fails: "The artifact name activation is not valid" — smoke-test fleet outage

2 participants