Skip to content

Add support for PyPI package publish #446

Draft
ShreyeshArangath wants to merge 1 commit intolinkedin:mainfrom
ShreyeshArangath:feat/pypi
Draft

Add support for PyPI package publish #446
ShreyeshArangath wants to merge 1 commit intolinkedin:mainfrom
ShreyeshArangath:feat/pypi

Conversation

@ShreyeshArangath
Copy link
Collaborator

@ShreyeshArangath ShreyeshArangath commented Feb 4, 2026

WIP: Summary

Add support for publishing the OH dataloader to PyPI on every commit.

Changes

  • Client-facing API Changes
  • Internal API Changes
  • Bug Fixes
  • New Features
  • Performance Improvements
  • Code Style
  • Refactoring
  • Documentation
  • Tests

Testing Done

Tested the Python release workflow locally using act:

  ### ✅ Test Python Packages
  - Python 3.12.12 setup successful
  - uv 0.9.30 installed
  - Dependencies synced (51 packages installed)
  - Linting: `All checks passed!`
  - Formatting: `9 files already formatted`
  - Tests: `1 passed in 0.00s`

  ### ✅ Tag Python Release
  - Version extracted: `0.1.0`
  - Output set correctly for downstream jobs

  ### ✅ Discover Python Packages
  - Discovered: `["integrations/python/dataloader"]`

  ### ✅ Build Python Package
  - Dependencies synced successfully
  - Version updated: `0.1.0`
  - Build artifacts created:
    - `openhouse_dataloader-0.1.0.tar.gz`
    - `openhouse_dataloader-0.1.0-py3-none-any.whl`
  - **Twine validation: PASSED** ✅
    - Wheel: `PASSED`
    - Source dist: `PASSED`

  ### ⏭️ Publish to PyPI
  - Skipped (requires actual GitHub Actions environment)

  ### Note
  - Upload artifacts step fails in `act` (expected - requires `ACTIONS_RUNTIME_TOKEN`)
  - All critical build and validation steps pass successfully
  • Manually Tested on local docker setup. Please include commands ran, and their output.
  • Added new tests for the changes made.
  • Updated existing tests to reflect the changes made.
  • No tests added or updated. Please explain why. If unsure, please feel free to ask for help.
  • Some other form of testing like staging or soak time in production. Please explain.

For all the boxes checked, include a detailed description of the testing done for the changes made in this pull request.

Additional Information

  • Breaking Changes
  • Deprecations
  • Large PR broken into smaller PRs, and PR plan linked in the description.

For all the boxes checked, include additional details of the changes made in this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant