Hi — the active release workflow still uses actions/upload-artifact@v3 here:
https://github.com/darkweak/souin/blob/master/.github/workflows/release.yml#L122
GitHub retired and blocked v1–v3 of the artifact actions on GitHub.com, so the generate-tyk-versions job can fail when the next tagged release runs:
https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
The minimal fix is to move that step to actions/upload-artifact@v4 and test the release workflow in a branch.
I found this through a public, no-login scan:
https://actions-breakage-radar.netlify.app/?repo=darkweak%2Fsouin
Disclosure: I operate the open-source scanner linked above. This issue is based on the exact workflow line and GitHub's official retirement notice, not an automated guess.
Hi — the active release workflow still uses
actions/upload-artifact@v3here:https://github.com/darkweak/souin/blob/master/.github/workflows/release.yml#L122
GitHub retired and blocked v1–v3 of the artifact actions on GitHub.com, so the
generate-tyk-versionsjob can fail when the next tagged release runs:https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
The minimal fix is to move that step to
actions/upload-artifact@v4and test the release workflow in a branch.I found this through a public, no-login scan:
https://actions-breakage-radar.netlify.app/?repo=darkweak%2Fsouin
Disclosure: I operate the open-source scanner linked above. This issue is based on the exact workflow line and GitHub's official retirement notice, not an automated guess.