-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat req] Enable v4 version for GHES before the v3 deprecation #641
Comments
👋🏼 From the change log:
There is no plan to deprecate Artifacts v3 in GitHub Enterprise Server, and the roadmap target date needs to be adjusted. |
Due to the removal of Node16 from the runners, upload-artifact@v3 has stopped working. |
Yep, this is exactly the reason about I'm asking it. |
F.Y.I.: there is a similar issue #537 |
Would it help to use v3-node20 version?
|
What would you like to be added?
Hello! According the first warning that we have in README.md, upload-artifact@v3 will be deprecated at the end of November.
What's the impact that we could expect for GHES implementations knowing that v4 is not currently supported in GHES yet?
We know the v4 version is expected to be enabled in Dec 2024 according to the roadmap, so I just want to prepare myself for possible scenarios in my implementation.
Why is this needed?
To be prepared for migration and deprecation scenarios in GHES implementations.
The text was updated successfully, but these errors were encountered: