feat: support Python 3.10 through 3.14#10
Merged
Conversation
Document the supported interpreter range in the README. The classifier and CI matrix for Python 3.14 landed in #9, but its squash-merge commit subject was not a valid Conventional Commit, so release-please could not parse it and skipped the release. This commit lands a parseable feat so the broadened Python support is captured in a release. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
bonyfusbouvet
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #9. The classifier and CI matrix for Python 3.14 landed there, but the squash-merge commit subject (
Expand Python version coverage to 3.10–3.14 (#9)) was not a valid Conventional Commit, so release-please could not parse it and skipped creating a release PR:(The
lint-prcheck only validates the PR title; since #9 had a single commit, GitHub's squash used that commit's non-conventional subject as the merge message.)This PR lands a parseable
feat:commit so release-please picks up the broadened Python support and opens the release PR (0.5.0 → 0.6.0).Changes
Installsection.Note
Recommend enabling Settings → "Default to PR title for squash merge commits" so a corrected PR title always becomes the merge message and this can't recur.