Skip to content

Conversation

@davidgamez
Copy link
Member

@davidgamez davidgamez commented Dec 1, 2025

Description

This PR introduces minimal automation of Python's PRs and releases. The release action will be tested after merging and might need some tweaks afterward. In this PR, the Python package version is intentionally not bumped. It will be bumped when the full CI is tested and ready for prime time.

From our AI friend

This pull request introduces a new set of GitHub Actions workflows to automate Python package testing and release processes. The main changes are the addition of reusable workflows for running tests on multiple Python versions, checking for version bumps in pyproject.toml during pull requests, and building and publishing the package to PyPI during releases.

CI/CD Workflow Additions:

  • Added .github/workflows/python-test.yml as a reusable workflow to run Python tests across multiple versions, with configurable inputs for package and test paths, and optional debug output.

Pull Request Checks:

  • Created .github/workflows/python-pr.yml to run tests via the reusable workflow and check if the package version in python/pyproject.toml was bumped in pull requests, warning if not.

Release Automation:

  • Introduced .github/workflows/python-release.yml to run tests and, upon success, build and publish the Python package to PyPI using trusted publishing via GitHub Actions.

@davidgamez davidgamez changed the title Add Python GitHub workflows chore(python): add Python GitHub workflows Dec 1, 2025
@davidgamez davidgamez marked this pull request as ready for review December 1, 2025 22:00
@davidgamez davidgamez requested review from cka-y, jcpitre and qcdyx December 2, 2025 19:20
@jcpitre
Copy link

jcpitre commented Dec 3, 2025

The reason we don't bump the version is because it will not be published to PyPI if the version did not change?

Copy link

@jcpitre jcpitre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a little question, but apart from that it looks ok.

@davidgamez
Copy link
Member Author

The reason we don't bump the version is because it will not be published to PyPI if the version did not change?

Yes, let's test the action first, then bump the version in a follow up PR

@davidgamez davidgamez merged commit 457a071 into master Dec 3, 2025
3 checks passed
@davidgamez davidgamez deleted the chore/python_release branch December 3, 2025 14:13
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.

3 participants