Skip to content

fix: remove run-id from download-artifact in deploy job - #8

Merged
RuBiCK merged 1 commit into
mainfrom
fix/deploy-artifact-download
Jun 15, 2026
Merged

fix: remove run-id from download-artifact in deploy job#8
RuBiCK merged 1 commit into
mainfrom
fix/deploy-artifact-download

Conversation

@RuBiCK

@RuBiCK RuBiCK commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Problem

The deploy job was failing with:

Unable to download artifact(s): Artifact not found for name: zarf-package-sha-eee9121

The download-artifact@v4 step had run-id: ${{ github.event.workflow_run.id }}, which resolves to the Build & Push Images run ID — the upstream workflow that triggered this one. That run has no Zarf tarball.

Fix

Remove run-id and github-token entirely. The package and deploy jobs are in the same workflow run, so download-artifact@v4 finds the artifact automatically by name within the current run — no run-id needed.

🤖 Generated with Claude Code

The package and deploy jobs are in the same workflow run. download-artifact@v4
finds artifacts by name within the current run automatically — no run-id or
github-token needed. Using github.event.workflow_run.id (the upstream
Build & Push run) caused artifact not found errors.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@RuBiCK
RuBiCK merged commit 027c773 into main Jun 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant