fix(ci): pin GitPython below 3.1.60 in the release step - #280
Closed
aaaaahaaaaa wants to merge 1 commit into
Closed
Conversation
GitPython 3.1.60 removed Actor.name_email_regex, which breaks every python-semantic-release config load inside the @v10 action's docker image (python-semantic-release/python-semantic-release#1476) — the Release workflow fails before versioning anything. Temporary workaround: run the exact CLI the action ran, via uvx with GitPython pinned (plus pip, which uv-managed venvs omit but the configured build_command bootstraps uv with). The released output is derived from the tag moving. Revert to the action once a PSR release carries upstream PR #1477. By Digitl
Contributor
Author
|
Superseded: main landed the equivalent workaround in 8774c13 (venv-based PSR run with gitpython==3.1.59) and 0.65.0 released with it. The revert-when-upstream-fixes note applies to that change now. |
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
1 participant
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
The Release workflow is currently broken by an upstream regression: GitPython 3.1.60 (released 2026-08-25) removed
Actor.name_email_regex, which crashes every python-semantic-release config load inside the@v10action's docker image — see PSR #1476. Today's 0.65.0 release dispatch failed with exactly this error; the fix (PSR #1477) is not yet merged or released.Temporary workaround: replace the action step with the exact CLI it ran (
semantic-release -v version --commit --tag --changelog --vcs-release --prerelease-token rc, per the action's own log), executed viauvxwithgitpython<3.1.60pinned. Details:--with pip: the configuredbuild_commandbootstraps uv viapython -m pip, and uv-managed venvs ship without pip.releasedoutput the publish gate reads is derived from whethergit describemoved.--no-changelog --as-prerelease) and theforceinput (--patch|--minor|--major) are mapped like the action's inputs.GH_TOKENmatch what the action injected; pushes ride the checkout's persisted app-token credentials.Revert to the action once a PSR release carries the upstream fix.
Context
This unblocks the 0.65.0 release, which the already-merged Flux MR (interloper/kubernetes!26) pins to deploy the MCP server at mcp.interloper.dev.
By Digitl