Add JFrog publish workflow for pyiceberg#45
Merged
robreeves merged 10 commits intolinkedin:li-0.11from Apr 3, 2026
Merged
Conversation
Publishes pyiceberg to the openhouse-pypi JFrog repository on each push to li-0.11, auto-incrementing the patch version via git tags.
robreeves
requested review from
ShreyeshArangath,
cbb330,
Copilot and
sumedhsakdeo
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a GitHub Actions workflow to automatically tag, build, and publish pyiceberg artifacts to the LinkedIn JFrog Artifactory PyPI repo (openhouse-pypi) on pushes to the li-0.11 branch.
Changes:
- Introduces a
tagjob that derives the initial version frompyproject.toml, bumps the patch version, and pushes a git tag. - Reuses the existing
pypi-build-artifacts.ymlreusable workflow to build sdist and multi-platform wheels for the computed version. - Publishes the built artifacts to JFrog Artifactory using
pypa/gh-action-pypi-publish.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Collaborator
|
We might want to add branch protection requiring at least one approval 
|
Collaborator
Author
@sumedhsakdeo added this today. I didn't have permission to do it. |
sumedhsakdeo
previously approved these changes
Apr 3, 2026
Follow LinkedIn's li* naming convention per PR feedback.
ShreyeshArangath
approved these changes
Apr 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
Publish the pyiceberg package to the same JFrog Artifactory PyPI repository (
openhouse-pypi) used by the OpenHouse data loader.The package is renamed from
pyicebergtoli-pyicebergto distinguish it from the upstream Apache release and follow LinkedIn'sli*naming convention. The Python import (import pyiceberg) is unchanged.How it works
pyproject.tomlas the initial version, then auto-increments the patch via git tags on each push toli-0.11(e.g.v0.11.1,v0.11.2, ...)pypi-build-artifacts.ymlto build sdist and multi-platform wheels (Linux, Linux ARM, Windows, macOS Intel, macOS ARM) across Python 3.10–3.13 via cibuildwheel. Each wheel is validated by runningpytest tests/avro/test_decoder.py.pypa/gh-action-pypi-publish. Jobs are sequenced vianeeds:so publish waits for all matrix builds to complete.This does not publish to PyPI or TestPyPI. The existing upstream workflows (
nightly-pypi-build.yml,python-release.yml) are gated bygithub.repository == 'apache/iceberg-python'and will not run in this fork.Requires
JFROG_USERNAMEandJFROG_PYPI_API_TOKENsecrets to be configured in this repo.Are these changes tested?
Will be validated on the first push to
li-0.11after secrets are configured.Are there any user-facing changes?
No.