Currently donwload-artifact action has changed their API and the path where the artifacts are being downloaded, has changed too. https://github.com/actions/download-artifact/releases/tag/v5.0.0
This affects the stacks/base images repositories, as the workflows expect the artifacts to be on a specific path. Therefore, by merging this PR #1258 , it creates PRs that do not land on base images, and therefore not additional PRs from github config can land.
For fixing that issue, the create-release workflow and the test-pull request workflow on the stacks/base images repositories needs to be patched first and ensure that the artifacts are being downloaded on the correct path by using the latest version of the upload and download artifact actions.
Currently donwload-artifact action has changed their API and the path where the artifacts are being downloaded, has changed too. https://github.com/actions/download-artifact/releases/tag/v5.0.0
This affects the stacks/base images repositories, as the workflows expect the artifacts to be on a specific path. Therefore, by merging this PR #1258 , it creates PRs that do not land on base images, and therefore not additional PRs from github config can land.
For fixing that issue, the create-release workflow and the test-pull request workflow on the stacks/base images repositories needs to be patched first and ensure that the artifacts are being downloaded on the correct path by using the latest version of the upload and download artifact actions.