fix: remove duplicate setup-uv from build action - #12
Merged
Conversation
The build action is always preceded by the CI action in every job. Running setup-uv a second time fails when trying to activate a venv that already exists. Removed setup-uv, uv lock, and uv sync from the build action since CI already handles all three. Co-authored-by: Cursor <cursoragent@cursor.com>
tracisiebel
approved these changes
Jul 31, 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.
Summary
The build action (
/.github/actions/build) included its ownastral-sh/setup-uv@v5step, but every job that uses the build action also uses the CI action first — which already runssetup-uv. The secondsetup-uvinvocation fails at "Activating python venv..." because the venv is already set up.This removes
setup-uv,uv lock, anduv syncfrom the build action entirely, leaving only theuv buildstep. The CI action handles all setup.Root cause