Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Question: why does uv.lock record the project's own version ? #10559

Closed
neutrinoceros opened this issue Jan 13, 2025 · 2 comments
Closed

Question: why does uv.lock record the project's own version ? #10559

neutrinoceros opened this issue Jan 13, 2025 · 2 comments

Comments

@neutrinoceros
Copy link

This is perhaps a naive question but I'm wondering why uv.lock would need to record the project's own version ?
This behavior is generating friction in projects that have a dynamic version number. I got bitten by it myself: astral-sh/uv-pre-commit#35
Any chance this could be relaxed somehow ?
@cb-robot
Copy link

FYI, this has been (and is still being) discussed extensively on #7533.

@neutrinoceros
Copy link
Author

thank you, I missed that one ! Let's close this one as a dupe then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cb-robot @neutrinoceros