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
Update ci version #16964
Update ci version #16964
Conversation
Signed-off-by: fengshunli <1171313930@qq.com>
Thank you for your pull request. |
may i ask what is the motivation or benefit from the newer versions? or perhaps the older versions are becoming deprecated? @fengshunli also please take notice of the request to sign the CLA. we cannot merge any contributions until the signed agreement is accepted, thanks. |
The v2 version is just a demo version, the 3 version solves some risks, is safer and has more complete functions |
this seems like the relevant news article regarding v2 -> v3: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ |
You can see that version 3 has solved a lot of dependency compatibility and loopholes see EPICLab/synectic#1030 |
CLA has been signed @Xenorith |
alluxio-bot, merge this please |
### What changes are proposed in this pull request? Please outline the changes and how this PR fixes the issue. Alluxio#16963 ### Why are the changes needed? Please clarify why the changes are needed. For instance, 1. If you propose a new API, clarify the use case for a new API. 2. If you fix a bug, describe the bug. ### Does this PR introduce any user facing changes? Please list the user-facing changes introduced by your change, including 1. change in user-facing APIs 2. addition or removal of property keys 3. webui pr-link: Alluxio#16964 change-id: cid-8da7ea42471d3b615289397def114ab384440f2f
### What changes are proposed in this pull request? Please outline the changes and how this PR fixes the issue. Alluxio#16963 ### Why are the changes needed? Please clarify why the changes are needed. For instance, 1. If you propose a new API, clarify the use case for a new API. 2. If you fix a bug, describe the bug. ### Does this PR introduce any user facing changes? Please list the user-facing changes introduced by your change, including 1. change in user-facing APIs 2. addition or removal of property keys 3. webui pr-link: Alluxio#16964 change-id: cid-8da7ea42471d3b615289397def114ab384440f2f
### What changes are proposed in this pull request? Please outline the changes and how this PR fixes the issue. Alluxio#16963 ### Why are the changes needed? Please clarify why the changes are needed. For instance, 1. If you propose a new API, clarify the use case for a new API. 2. If you fix a bug, describe the bug. ### Does this PR introduce any user facing changes? Please list the user-facing changes introduced by your change, including 1. change in user-facing APIs 2. addition or removal of property keys 3. webui pr-link: Alluxio#16964 change-id: cid-8da7ea42471d3b615289397def114ab384440f2f
### What changes are proposed in this pull request? Please outline the changes and how this PR fixes the issue. Alluxio#16963 ### Why are the changes needed? Please clarify why the changes are needed. For instance, 1. If you propose a new API, clarify the use case for a new API. 2. If you fix a bug, describe the bug. ### Does this PR introduce any user facing changes? Please list the user-facing changes introduced by your change, including 1. change in user-facing APIs 2. addition or removal of property keys 3. webui pr-link: Alluxio#16964 change-id: cid-8da7ea42471d3b615289397def114ab384440f2f
What changes are proposed in this pull request?
Please outline the changes and how this PR fixes the issue.
#16963
Why are the changes needed?
Please clarify why the changes are needed. For instance,
Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including