fix(py/handlebarrz): remove redundant lock file #360
Merged
Conversation
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
RATIONALE:
It appears that there is a redundant lock file in
python/handlebarrz/uv.lock file. However, running
`uv sync` doesn't appear to make any changes to the file.
uv manages lock files at the workspace level so it
appears to be safe to delete this file.
CHANGELOG:
- [ ] Remove the uv.lock file from the project-specific
directory and use the workspace one.
yesudeep
force-pushed
the
yesudeep/fix/noiseless-offer
branch
from
c3f5072 to
ed6599d
Compare
MengqinShen
approved these changes
Nov 21, 2025
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.
fix(py/handlebarrz): remove redundant lock file
RATIONALE:
It appears that there is a redundant lock file in
python/handlebarrz/uv.lock file. However, running
uv syncdoesn't appear to make any changes to the file.uv manages lock files at the workspace level so it
appears to be safe to delete this file.
CHANGELOG:
directory and use the workspace one.