kevinjqliu commented on issue #872: URL: https://github.com/apache/iceberg-python/issues/872#issuecomment-2229051951
Based on [this tutorial](https://medium.com/@blackary/publishing-a-python-package-from-github-to-pypi-in-2024-a6fb8635d45d), I was able to publish new versions of the library to PyPi via Github Action. Here are the relevant steps: I created an account on Pypi and was able to publish my forked repo of Pyiceberg using the `pypi-publish` GitHub Action. To do so, I created [`.github/workflows/publish.yml` file](https://github.com/kevinjqliu/iceberg-python/blob/main/.github/workflows/publish.yml) and pushed it to my forked repo's main branch. I had to change the package name to `pyiceberg-kevinliu` to not conflict with the existing package. I set up "Trusted Publisher Management" via the Pypi website for my forked repo. On the forked repo, I created a new release and tag, named ["v0.6.1"](https://github.com/kevinjqliu/iceberg-python/releases/tag/v0.6.1). This kicks off the [Github Action to publish to Pypi](https://github.com/kevinjqliu/iceberg-python/actions/runs/9932636287/job/27434240091) Resulting in this new package https://pypi.org/project/pyiceberg-kevinliu/ -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
