Repository navigation
fix(webhooks): remove obsolete flags in scored schema 2026-10-08 - #22
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
1 participant
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.
New identification.scored payloads use schema 2026-10-08 and omit browser_vpn_proxy, datacenter_ip, abuser and suspicious_paid_click from detection_flags. vpn includes Browser VPN/Proxy in flags, connection_type and signals; site_id remains available for receivers handling multiple sites.
The new version forbids the removed keys and separate browser_vpn_proxy connection type/signal, while historical bodies remain readable through deprecated compatibility properties. Multiaccount stays on 2026-10-07. Includes Core-generated fixtures and rebuilt distribution schemas.
Validation: npm run bundle, npm run lint, npm test (75 passing).