Skip to content

ci: publish with a Python the runner has - #98

Merged
ClayMav merged 1 commit into
mainfrom
fix/publish-python-version
Nov 18, 2026
Merged

ClayMav merged 1 commit into
mainfrom
fix/publish-python-version

Conversation

@ClayMav

@ClayMav ClayMav commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Summary

Pushing tag v0.33.0 did not publish to PyPI. The publish workflow asks for Python 3.8, and ubuntu-latest moved to Ubuntu 26.04, which has no 3.8 (failed run):

The version '3.8' with architecture 'x64' was not found for Ubuntu 26.04.

The package needs Python 3.10 or newer anyway, so the workflow now sets up 3.12 with setup-python@v5, the same setup test.yaml runs on that runner today.

The v0.33.0 tag points at a commit with the old workflow, so 0.33.0 still needs its tag moved to this fix once it merges.

Related Issues

None.

Verification

  • uv build --python 3.12 in this branch builds wherobots_python_dbapi-0.33.0.tar.gz and wherobots_python_dbapi-0.33.0-py3-none-any.whl.
  • The latest test run on main ran on ubuntu-26.04, set up CPython 3.12.16 with setup-python@v5, installed uv 0.7.12 and ran uv build.
  • Not run: the publish job itself. It only runs on a tag push, so the tag comparison step and the PyPI upload are first exercised when the tag moves.
  • Independent agent review found no blocking problems. It confirmed the 0.32.0 artifacts were built by uv on 3.12.3, not 3.8, so the built wheel and sdist do not change. Wheel metadata for 0.33.0 differs from 0.32.0 on PyPI only in Version.

Requester Checklist

  • I have self-reviewed my own code
  • I have added/updated tests that prove my fix/feature works (CI config only, see Verification)
  • I have included visual proof (screenshot, video, or test output) if applicable
  • All CI checks are passing
  • PR size is S/M, OR I have justified the size and added a walkthrough
  • I have updated documentation if needed (none needed)

Written by Claude Fable 5.2 in Claude Code (T3 Code).

@ClayMav ClayMav added the please-rubber-stamp Safe changes eligible for a quick review label Nov 18, 2026
@ClayMav
ClayMav requested a review from a team November 18, 2026 16:48
@ClayMav

ClayMav commented Nov 18, 2026

Copy link
Copy Markdown
Member Author

@salty-hambot review

@ClayMav ClayMav added the please-rubber-stamp Safe changes eligible for a quick review label Nov 18, 2026

@salty-hambot salty-hambot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Reviewed by Salty Hambot 🤖🧂 at 6dbbe66

No issues found.
💰 $0.0269 · 17.2k in / 713 out tokens · ⏱️ 8.9s · us.openai.gpt-6-sol high, prompt coverage-v1
💬 To request a re-review, comment @salty-hambot review

@ClayMav
ClayMav marked this pull request as ready for review November 18, 2026 16:50
@ClayMav
ClayMav merged commit a96dccc into main Nov 18, 2026
7 checks passed
@ClayMav
ClayMav deleted the fix/publish-python-version branch November 18, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

please-rubber-stamp Safe changes eligible for a quick review

Development

Successfully merging this pull request may close these issues.

2 participants