GitHub Actions: artifact not found in another job
Build saves the file, but the next job cannot download it or fetch an outdated artifact. Artefacts are associated with a specific workflow run, name and retention periods.
How to determine the source of the error
Check that the upload-artifact has been successfully completed in the same run and what name is assigned.
Determine whether calling download-artifact indicates correct run ID and available permissions.
What to do step by step
1. Unify the name of the artifact between jobs and transfer the depositors through needs so that download does not run before upload.
2 . When downloading from another workflow, give out the token and the corresponding run ID from the corresponding repo.
How to check the score
Another job reads exactly the artifact of the current build and does not pull out random old files.
What to do
Do not replace artifacts with publishing tokens or private data in the log.