You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: GitPython v3.1.60 removed Actor.name_email_regex, breaking every config load #1476
GitPython v3.1.60 (released 2026-08-25) removed the name_email_regex class attribute from git.Actor, replacing its internal use in Actor._from_string with string partitioning. RuntimeContext.from_raw_config() reads that attribute unconditionally, so everysemantic-release command that loads configuration now fails.
Error: type object 'Actor' has no attribute 'name_email_regex'
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.
GitPython
Result
3.1.59
config loads
3.1.60
AttributeError
Reproduction
The repository's own test suite reproduces it — no new test needed:
$ pip install 'gitpython==3.1.60'
$ pytest tests/unit/semantic_release/cli/test_config.py -k commit_authorE AttributeError: type object 'Actor' has no attribute 'name_email_regex'src/semantic_release/cli/config.py:745: AttributeError
Impact on the GitHub Action
The official action is hit hardest. src/gh_action/Dockerfile installs from src/gh_action/requirements.txt, which pins only python-semantic-release == 10.5.3 and 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.const rather than reaching into GitPython's internals — GitPython no longer exposes any public equivalent, so there is nothing to migrate to. PR incoming.
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
Activity
[BUG] Stop resolving GitPython at PSR Docker image build time
fix(ci): run semantic-release from the locked environment
fix(ci): run semantic-release from the locked environment
fix(ci): pinned GitPython below 3.1.60 for release
fix(ci): replaced GitPython pin with a compat shim
qthequartermasterman commentedon Aug 26, 2026
@codejedi365 This gitpython version incompatibility is breaking releases for anyone using the github action that builds its own docker image.
ci: run semantic-release directly with GitPython pinned
fix: run PSR via uv to work around upstream GitPython break
fix: bound upper version for problematic gitpython vs semantic-releas…
fix: bound upper version for problematic gitpython vs semantic-releas…
fix: bound upper version for problematic gitpython vs semantic-releas…
fix(config): validate commit author in config internally
ci(validate): adjust github action reference to use current HEAD for …
ci(release): adjust github action reference to use current HEAD for a…
ci(validate): adjust github action reference to use current HEAD for …
5 remaining items
fix: create GitHub release with assets attached, not after publish
fix: create GitHub release with assets attached, not after publish
fix: create GitHub release with assets attached, not after publish
blf778 commentedon Aug 28, 2026
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.fix(config): validate commit author in config internally
fix(config): validate commit author in config internally
fix(config): validate commit author in config internally
fix(config): validate commit author in config internally (python-sema…
codejedi365 commentedon 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.
🔧 chore(ci): python-semantic-release 액션 pin을 v10.6.2로 업데이트
feat: modernize Python tooling to uv + pyproject.toml + semantic-rele…