Skip to content

ci: scope UV_PRERELEASE to Python 3.15 in unittest workflow - #18529

Merged
ohmayr merged 4 commits into
mainfrom
ci/scope-uv-prerelease-to-python-315
Sep 30, 2026
Merged

ohmayr merged 4 commits into
mainfrom
ci/scope-uv-prerelease-to-python-315

Conversation

@ohmayr

@ohmayr ohmayr commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Context & Problem

A top-level UV_PRERELEASE: "allow" was previously set on .github/workflows/unittest.yml to support Python 3.15. However, because it was set at the top-level workflow environment, uv resolved prerelease packages (such as pandas 3.1.0rc0) across all Python 3.10-3.14 unit test runs, causing unintentional test breakage on stable Python shards.

@ohmayr
ohmayr requested a review from a team as a code owner September 30, 2026 22:41
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@ohmayr
ohmayr force-pushed the ci/scope-uv-prerelease-to-python-315 branch from ab24811 to 1e4526c Compare September 30, 2026 22:51
Remove global UV_PRERELEASE: allow from top-level workflow env and
scope it strictly to Python 3.15 unit tests until Python 3.15 is officially
released with stable upstream binary wheels.

Fixes #18532
Enable UV_PRERELEASE=allow via a conditional step only on Python 3.15
matrix shards to avoid pulling prerelease versions on stable Python
versions while preventing empty string UV_PRERELEASE export errors.

Fixes #18532
@ohmayr
ohmayr merged commit 849a7dd into main Sep 30, 2026
112 checks passed
@ohmayr
ohmayr deleted the ci/scope-uv-prerelease-to-python-315 branch September 30, 2026 23:25
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.

2 participants