fix(ci,#1035): clear production npm audit gate#1305
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
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
sqlite3and@types/sqlite3dependencies; the codebase usesbetter-sqlite3and has no rootsqlite3imports.edge-tts-nodetransitive crypto-browserify/elliptic findings visible for follow-up replacement work.Why
#1035 is blocked by
npm audit --omit=dev --audit-level=high. The high/critical findings are independent of the Docker image freshness blocker and can be fixed on canary now.Verification
npm cinpm audit --omit=dev --audit-level=highgit diff --checknpm run build:tsNotes
scripts/push-current-arch.shfor stale:pr-1035images before Carl install smoke can test the current canary bits.