Skip to content

CI: artefact uploads fail on re-run (set overwrite: true) #15

Open

Description

@woook

From CodeRabbit on PR #12 (.github/workflows/release.yml:90, #12 (comment)):

actions/upload-artifact v4 rejects a second artefact with the same name in one workflow run, and "Re-run failed jobs" counts as the same run.

  • release.yml: the evidence is uploaded as release-artefacts-${{ github.sha }} before gh release upload attaches it to the release. If the attach step fails, a re-run fails at the upload step and the evidence is never attached.
  • pytest.yml security job: release-evidence-${{ github.sha }} is uploaded with if: always(), so a re-run after any failed step fails the same way.

Fix: add overwrite: true to both actions/upload-artifact steps (supported by the pinned v4.5.0).

Not urgent for v1.1.1: CI-only, so the tested app (app-JFjp36j4Qj5J399jXzp8JXYZ) is unaffected. If the v1.1.1 release run fails part-way and needs a re-run, delete the existing artefact first, or attach sbom.json, requirements-hashed.txt and asset-requirements.txt to the release by hand with gh release upload.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions