fix: run PSR via uv again now that 10.6.2 fixes the GitPython break - #439
fix: run PSR via uv again now that 10.6.2 fixes the GitPython break#439irfanuddinahmad wants to merge 2 commits into
Conversation
openedx#438 reverted all the way back to the official Docker-based action once upstream fixed python-semantic-release/python-semantic-release#1476, but that wasn't necessary -- it also undid the uv-based invocation and build_command from openedx#435/openedx#436 for no reason tied to the actual bug. The gitpython pin was only ever needed to work around the bug; with PSR 10.6.2 (which no longer references the removed GitPython attribute) that constraint isn't needed at all, uvx resolves and runs it cleanly. Verified both halves locally: `uvx --from "python-semantic-release==10.6.2" ...` runs without error, and `SETUPTOOLS_SCM_PRETEND_VERSION=... uv build` produces correct dist/ artifacts. Keeping the uv-based invocation avoids reintroducing pip anywhere in this workflow (the official action's Docker image only has pip, not uv), consistent with this org's uv-native CI standard.
openedx-webhooks
added
open-source-contribution
|
Thanks for the pull request, @irfanuddinahmad! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
…tore-uv-psr-invocation
2 participants
Summary
Now that upstream ships a fix for the GitPython break (python-semantic-release#1476, released in PSR 10.6.2), run
python-semantic-releaseitself throughuvrather than the official Docker-based action -- consistent with the rest of this repo's uv migration, and avoids that action's Docker image, which only bundles pip, not uv.build_commandstays onuv buildaccordingly, so there's no pip anywhere in the release path.Verified locally:
uvx --from "python-semantic-release==10.6.2" semantic-release --noop -v version --no-changelog --no-vcs-releaseresolves cleanlySETUPTOOLS_SCM_PRETEND_VERSION=... uv buildproduces correctdist/artifactsTest plan
master(this commit itself,fix:type) cuts a real release and exercises the uv-based release path end-to-end