chore: fix false positive npm-ci check - #64
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the lockfile allowlist used by the code-scanning package’s lockfile validation logic, likely to avoid triggering an external CI check via keyword matches in source comments.
Changes:
- Removed inline “// npm/yarn/pnpm/bun” comments from the
LOCK_FILESconstant invalidate-lock-files.ts.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
r-farkhutdinov
approved these changes
Aug 20, 2026
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.
Practical Value
Should fix this: https://github.com/DevExpress/jssecurity/actions/runs/32314092084
Before
After