Repository navigation
fix: remove sensitive query logs and patch dependencies - #60
Merged
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.
Remove clear-text Salesforce query logging and patch the application/container dependency graph. Queries now emit a fixed diagnostic message, with a regression test preventing configured fields and billing-account IDs from entering logs. Update Node 26 / Alpine 3.24, Prisma 7.10.1 and the reviewed immutable core-library revision while retaining the existing external Prisma-client commit pins.
Replace obsolete ESLint/Ajv patches with patched compatible Ajv releases and add a tested minimatch adapter. Update stale metadata test expectations to match the already-retired event publisher; production metadata event behavior is unchanged.
Validation:
Targets the active
devbranch. GitHub code scanning will validate the logging remediation on this PR. No deployment or production data changes.