By default, can 'actions/download-artifact' access artifacts from a different workflow run?
Select an answer to reveal the explanation.
Short Explanation
The actions/download-artifact v4+ action added a run-id parameter — you can specify any run's ID to download its artifacts cross-run.
Full Explanation
actions/download-artifact v4+ adds run-id, letting you download artifacts from any workflow run in the same repository, not just the current run. The workflow needs actions: read permission. This supports patterns like downloading nightly-build artifacts, using outputs from a prior approved run for deployment, or fetching test fixtures from another workflow. Without run-id, it uses the current run. Cross-repository artifact access is not natively supported. Access is not limited to the uploading job; branch alone is not enough; and artifacts can be shared across runs or workflows within the same repository when run-id and permissions are used.