Skip to content

Recommend --locked over --frozen for uv sync#972

Merged
henryiii merged 1 commit intowntrblm:mainfrom
johnthagen:patch-1
May 13, 2025
Merged

Recommend --locked over --frozen for uv sync#972
henryiii merged 1 commit intowntrblm:mainfrom
johnthagen:patch-1

Conversation

@johnthagen
Copy link
Contributor

This tracks upstream recommendations

To be honest, I actually think that we should put --locked into the default code example above this paragraph. An out-of-date lockfile is something you almost always want to catch in CI or locally with a tool like Nox.

@henryiii what do you think?

For now, this PR takes the more conservative change of simply recommending --locked over --frozen.

Copy link
Contributor

@edgarrmondragon edgarrmondragon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense. I recently found that I was using UV_PRERELEASE=allow in CI but not locally.

@henryiii
Copy link
Collaborator

What is the default? And what happens if there isn't a lockfile yet? I think the default is like --frozen except it creates the lockfile the first time it runs, which is probably useful if people are just using nox and not running uv directly.

@henryiii henryiii merged commit 4fb4e42 into wntrblm:main May 13, 2025
21 checks passed
@johnthagen johnthagen deleted the patch-1 branch May 13, 2025 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants