chore: uv acceptance test #6413
Merged
+327
−1
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/bump-os-uv-acceptance
branch
3 times, most recently
from
e8ad3cb to
c87b073
Compare
snyk-will
force-pushed
the
chore/bump-os-uv-acceptance
branch
from
c87b073 to
13cb05f
Compare
snyk-tim
approved these changes
Jan 8, 2026
Collaborator
|
The PR title mentions a bump for os-flows, but I'm guessing that is done though #6419? 🤔 |
snyk-will
changed the title
Contributor
Author
|
@CatalinSnyk that PR is unrelated to my change actually. I think os flows beat me to the update so the version I needed is actually already merged, I can update pr title |
CatalinSnyk
approved these changes
Jan 8, 2026
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?
In the latest version of the os-flows extension we have introduced a registry feature flag and removed the need for an environment variable and the experimental flag. This PR adds an acceptance test to check the implementation of the feature flag and the correct routing of the uv workflow through os-flows to the unified test API.
What's the product update that needs to be communicated to CLI users?
None, the feature has not yet reached closed beta
Risk assessment (Low)?
Low, just acceptance tests
What are the relevant tickets?
https://snyksec.atlassian.net/browse/UNIFY-1117
https://snyksec.atlassian.net/browse/UNIFY-1118