Repository navigation
Bug: GitPython v3.1.60 removed Actor.name_email_regex, breaking every config load #1476
Description
Activity
- added a commit that references this issue
on Aug 25, 2026 - added 2 commits that reference this issue
on Aug 26, 2026 - added 2 commits that reference this issue
on Aug 26, 2026 @codejedi365 This gitpython version incompatibility is breaking releases for anyone using the github action that builds its own docker image.
Reacted by Heinz-Alexander Fuetterer and Mike Patrick- added a commit that references this issue
on Aug 27, 2026 - added a commit that references this issue
on Aug 27, 2026 - added a commit that references this issue
on Aug 27, 2026 - added 4 commits that reference this issue
on Aug 28, 2026 5 remaining items
For what it's worth, GitPython released an update on August 28th at 0704 EDT (1104 UTC) that rolls back the change to
Actorand makes it depricated.Reacted by Andrew Sansom, Bruno Alla and Heinz-Alexander Fuetterer- added a commit that references this issue
on Aug 28, 2026 🎉 This issue has been resolved in v10.6.2 🎉
You can find more information about this release on the GitHub Releases page.
If your issue persists, please reply here and we will re-open the issue. If you receive a new error, please open a new issue and reference this issue there.
Reacted by Heinz-Alexander Fuetterer, benkozi and pricealexandra- added a commit that references this issue
on Aug 29, 2026 - marked AttributeError: type object 'Actor' has no attribute 'name_email_regex' (GitPython 3.1.60) #1475 as a duplicate of this issue
on Aug 29, 2026 - added a commit that references this issue
on Sep 21, 2026
Summary
GitPython v3.1.60 (released 2026-08-25) removed the
name_email_regexclass attribute fromgit.Actor, replacing its internal use inActor._from_stringwith string partitioning.RuntimeContext.from_raw_config()reads that attribute unconditionally, so everysemantic-releasecommand that loads configuration now fails.Since PSR requires
gitpython ~= 3.0, a fresh install resolves to the broken version.Affected versions
Reproduced on v10.5.3, v10.6.1, and current
master(c74aa3b) — the line is unchanged across all three.AttributeErrorReproduction
The repository's own test suite reproduces it — no new test needed:
Impact on the GitHub Action
The official action is hit hardest.
src/gh_action/Dockerfileinstalls fromsrc/gh_action/requirements.txt, which pins onlypython-semantic-release == 10.5.3and lets transitive dependencies resolve at image-build time. Because the image is built on the runner at job start, pinned workflows that have not changed in months started failing the moment 3.1.60 was published, and there is no input or config key that lets a caller constrain what lands inside the image. Callers currently have to vendor or fork the action to pin GitPython.Proposed fix
Keep an equivalent regex in
semantic_release.constrather than reaching into GitPython's internals — GitPython no longer exposes any public equivalent, so there is nothing to migrate to. PR incoming.