chore(ci): add workflow to validate uv.lock and check for regressions#73
Conversation
|
🎉 Welcome to the Kubeflow MCP Server! 🎉 Thanks for opening your first PR! We're happy to have you as part of our community 🚀 Here's what happens next:
Join the community:
Feel free to ask questions in the comments if you need any help or clarification! |
a1bd074 to
2176076
Compare
|
@Krishna-kg732 is there any suggestions on this ?? i saw the notification from your side but comment is removed ig! |
|
no , i had added a comment and then reomved it. |
|
/ok-to-test |
|
Thanks @priyank766 , Looks good ! t One ask before merge: can you rebase on latest main, bump Btw have you tested this PR? Could you either temporarily drop the path filter for one push or touch pyproject.toml on your fork so we see a green |
2176076 to
af437d8
Compare
|
Updated setup-uv to v7, and touched pyproject.toml. All checks are green now! |
Signed-off-by: priyank <priyank8445@gmail.com>
af437d8 to
b0e8210
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhijeet-dhumal The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Adds a CI workflow (
validate-lockfile.yaml) that triggers on pull requests whenuv.lockorpyproject.tomlare modified.The workflow performs two checks:
uv.lockfile is fully in sync withpyproject.tomlusinguv lock --check.uv audit, compares the results, and posts a warning comment on the PR detailing any newly introduced vulnerabilities.This follows the established pattern in
kubeflow/sdkto prevent merging stale or insecure lockfiles.Related Issue
Fixes #61
Testing
Manually verified
uv lock --checkruns successfully on the local environment.