fix: prevent uv version from triggering full dependency sync in publish workflow#51
Open
acere wants to merge 1 commit intoawslabs:mainfrom
Open
fix: prevent uv version from triggering full dependency sync in publish workflow#51acere wants to merge 1 commit intoawslabs:mainfrom
acere wants to merge 1 commit intoawslabs:mainfrom
Conversation
uv version without --no-sync modifies pyproject.toml and triggers an automatic sync, resolving and installing all 280+ dependencies unnecessarily in the publish workflow.
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.
Problem
uv versionmodifiespyproject.toml, which triggers uv to automatically sync the full dependency tree (280+ packages including numpy, pandas, scikit-learn, etc.) — none of which are needed for building and publishing.Fix
Add
--no-synctouv versionso it only updates the version string without resolving/installing dependencies.This makes the publish workflow significantly faster and avoids pulling unnecessary packages.