By default, can 'actions/download-artifact' access artifacts from a different workflow run?
Select an answer to reveal the explanation.
Short Explanation and Infographic
actions/download-artifact v4 added a run-id parameter — specify any run's ID to download its artifacts cross-run.
Full explanation below image
Full Explanation
actions/download-artifact (v4+) supports a 'run-id' parameter that allows downloading artifacts from any workflow run in the repository, not just the current run. The workflow must have 'actions: read' permission to access artifacts from other runs. This enables patterns like: downloading pre-built artifacts from a nightly build run, accessing build outputs from a previous approved run for deployment, or downloading test fixtures generated by a separate workflow. Without specifying 'run-id', it defaults to the current workflow run. Cross-repository artifact access is not supported natively.