You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering an issue when deploying my GitHub Pages site using actions/deploy-pages@v2. My workflow file references the following versions:
actions/checkout@v4
actions/configure-pages@v4
actions/upload-pages-artifact@v2
actions/deploy-pages@v2
However, during runtime the job fails with the following error:
I've verified that my workflow file contains no reference to any v3 action, and a full-text search in my repository shows no trace of "v3" in my workflow files. This indicates that the deprecated reference is being invoked internally within the composite action.
Could you please update the internal reference so that deploy-pages no longer depends on actions/upload-artifact@v3? Alternatively, is there a recommended migration strategy or workaround we should adopt?
Thank you for your help!
Best,
Simon
The text was updated successfully, but these errors were encountered:
Hi team,
I'm encountering an issue when deploying my GitHub Pages site using actions/deploy-pages@v2. My workflow file references the following versions:
actions/checkout@v4
actions/configure-pages@v4
actions/upload-pages-artifact@v2
actions/deploy-pages@v2
However, during runtime the job fails with the following error:
"This request has been automatically failed because it uses a deprecated version of actions/upload-artifact: v3. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/"
I've verified that my workflow file contains no reference to any v3 action, and a full-text search in my repository shows no trace of "v3" in my workflow files. This indicates that the deprecated reference is being invoked internally within the composite action.
Could you please update the internal reference so that deploy-pages no longer depends on actions/upload-artifact@v3? Alternatively, is there a recommended migration strategy or workaround we should adopt?
Thank you for your help!
Best,
Simon
The text was updated successfully, but these errors were encountered: