fix: resolve dependency and secret alerts#351
Merged
santoshkumarradha merged 2 commits intomainfrom Apr 7, 2026
Merged
Conversation
Contributor
Performance
⚠ Regression detected:
|
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
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.
Summary
glob,lodash, andyamlresolutions onto patched versionsvite@^6.4.2andvitest@^3.2.4, updating the npm lockfile away from vulnerablevite/esbuildentries while keeping the Node 18-compatible Vite 6 lineOPENROUTER_API_KEYVerification
control-plane/web/client/pnpm-lock.yamlwith Ruby YAMLsk-or-v1-secrets are absent from the touched filesgit diff --checkNotes
npm/pnpminstall-based verification was not possible here because registry access from the sandboxed package managers timed out / was unavailable