fix: bump tsx to clear esbuild Self Scan failures#639
Merged
Conversation
New OSV entries for esbuild@0.27.4 (via tsx) were failing CI jobs that run cve-lite with --fail-on high against the root package-lock.json. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Jun 12, 2026
sonukapoor
approved these changes
Jun 13, 2026
sonukapoor
left a comment
sonukapoor
left a comment
Collaborator
There was a problem hiding this comment.
Good catch and good call separating this into its own PR. Self-scan passing confirms the fix works.
Collaborator
|
Merged - thank you @Ayush7614! |
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
2 participants
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
Fixes failing Self Scan / self-scan-action CI jobs caused by new high-severity OSV advisories on
esbuild@0.27.4(transitive viatsx@4.21.0).Context
Recent advisories (
GHSA-g7r4-m6w7-qqqr,GHSA-gv7w-rqvm-qjhr) cause--fail-on highto exit 1 when scanning the rootpackage-lock.json. This affects open docs PRs (e.g. #594) even though they do not touch the root lockfile.Fix
Verified locally:
node dist/index.js . --fail-on high→ exit 0.Test plan
npm ci && npm run buildunchangedMade with Cursor