lhotari opened a new issue, #23314: URL: https://github.com/apache/pulsar/issues/23314
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation GitHub is deprecating existing v1, v2, and v3 upload actions. https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/ explains more. ``` [Deprecation notice: v1, v2, and v3 of the artifact actions] ... Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/ ``` ### Solution Pulsar CI uses a custom "GitHub Actions Artifact client", https://github.com/apache/pulsar-test-infra/tree/master/gh-actions-artifact-client . Instead of using the actual action, it uses the GitHub provided javascript library to create a custom client that can be used in shell scripts to upload and download any files to be cached during a workflow run. This is used in Pulsar CI to build the docker images once so that they can be used in the integration test and system test jobs. It's also used to share the binary build results. This action will need to be updated to use the v4 client libraries. ### Alternatives - ### Anything else? It's simply about updating the custom client that is written in Javascript. The model in the new v4 is slightly different, but it is possible to find a way which works for the new backend. ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
