chore: more uv acceptance tests #6476
Merged
+46
−0
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
snyk-will
force-pushed
the
chore/more-uv-acceptance-tests
branch
5 times, most recently
from
2e36f9d to
5b936c2
Compare
PeterSchafer
approved these changes
Jan 28, 2026
snyk-will
force-pushed
the
chore/more-uv-acceptance-tests
branch
from
5b936c2 to
447c84c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Some additional acceptance tests for edge cases with uv tests,
Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?
Risk assessment (Low | Medium | High)?
Low
Any background context you want to provide?
What are the relevant tickets?
https://snyksec.atlassian.net/browse/UNIFY-1153