Repository navigation
chore: pin gitpython below 3.1.60 for release bump - #324
Merged
Merged
Conversation
python-semantic-release 10.6.1 references git.Actor.name_email_regex during config validation, but GitPython removed that attribute in 3.1.60. The bump workflow installs requirements-release.txt with no gitpython bound, so pip resolved 3.1.60 and the NextSemver step failed with: type object 'Actor' has no attribute 'name_email_regex' Pin gitpython < 3.1.60 until python-semantic-release drops the reference. Signed-off-by: Karthik BekalPattathana <133984042+karthikbekalp@users.noreply.github.com>
leon-li-inspire
approved these changes
Aug 26, 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.
Problem
The release version-bump workflow fails on the
NextSemverstep (failed run):This is upstream dependency drift — nothing in this repo changed to cause it:
python-semantic-release10.6.1 (latest) readsgit.Actor.name_email_regexunconditionally during config validation (semantic_release/cli/config.py:745) and requires onlygitpython ~= 3.0, with no upper bound within the 3.x line.Actor.name_email_regexclass attribute. Every version 3.1.44–3.1.59 has it; only 3.1.60 dropped it.requirements-release.txthad no gitpython bound, so the bump workflow'spip installresolvedgitpython==3.1.60at run time andsemantic-release --strict versionhit theAttributeErrorand exited 1.Upgrading
python-semantic-releasedoes not help: 10.6.1 is the latest and still carries the reference.Upstream status
The break is tracked upstream and a fix is in flight, but not yet released:
Fix
Pin
gitpython < 3.1.60inrequirements-release.txtuntilpython-semantic-releaseships a release that drops thename_email_regexreference.Verification
A clean-venv install of the updated
requirements-release.txtresolvesgitpython==3.1.59(attribute present) alongsidepython-semantic-release==10.6.1, and thesemantic-releaseCLI loads correctly.Follow-up
Once
python-semantic-releasecuts a release including #1477, bumppython-semantic-releaseand remove thegitpython < 3.1.60pin.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.