Skip to content

Chore: test a single python version on PRs#2603

Merged
mivds merged 2 commits intomainfrom
chore/optimize-pr-ci
Feb 26, 2026
Merged

Chore: test a single python version on PRs#2603
mivds merged 2 commits intomainfrom
chore/optimize-pr-ci

Conversation

@mivds
Copy link
Contributor

@mivds mivds commented Feb 25, 2026

Change github workflow to only test a single python version on PR, rather than all supported versions. Commits to main continue to test all supported python versions.

@mivds mivds self-assigned this Feb 25, 2026
@mivds mivds requested review from AidaPaul and m1n0 February 26, 2026 09:16
Copy link
Contributor

@m1n0 m1n0 left a comment

Choose a reason for hiding this comment

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

I like the approach, but shouldn't we do 3.12 on PRs instead?

@mivds
Copy link
Contributor Author

mivds commented Feb 26, 2026

I like the approach, but shouldn't we do 3.12 on PRs instead?

No idea which is likely to cause the most issues to be honest (oldest vs newest). I'll follow your suggestion and update to 3.12

@sonarqubecloud
Copy link

@mivds
Copy link
Contributor Author

mivds commented Feb 26, 2026

@m1n0 Since python 3.13 and 3.14 are also already out there, I changed to:

  • PR test on Python 3.14
  • Main test on Python 3.10 - 3.14 (5 versions)

3.14 seems to work based on a local test (against postgres), but will see what CI does.

Copy link
Contributor

m1n0 commented Feb 26, 2026

no objections, although I had some issues with black on 3.14 locally, but I haven't invested into figuring it out

@mivds mivds merged commit a636328 into main Feb 26, 2026
19 checks passed
@mivds mivds deleted the chore/optimize-pr-ci branch February 26, 2026 10:53
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