Repository navigation
Prepare Node SDK 1.1.0 for the current identification contract - #15
Merged
Merged
Conversation
EgorMajj
marked this pull request as ready for review
October 27, 2026 23:17
KonstantinSerebryakov
approved these changes
Oct 28, 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.
The published 1.0.1 package can leave normalized identification IDs empty on the current API payload. Prepare the 1.1.0 candidate from current main with canonical identification_id and the current 20 detection flags. No npm release is performed.
Adds a synthetic current public webhook fixture and regressions for ID/raw preservation, Node/edge parsing, current flags, legacy History input, opaque production event IDs and version consistency. Production event_id can be a stable 40-character hex string; Portal Test may use a UUID. Consumers must not impose a UUID format on the event key.
Validation: 680 tests; TypeScript, ESLint/Prettier, build, package installation and Node/edge runtime checks. The previous clean React/Vite + Node/SQLite app on OrbStack completed two real History/MCP chains with matching IDs (100/Dangerous in automated Chromium). The edge candidate also verified real external deliveries from two registered production sites; browser, webhook and MCP IDs matched, both scores 30/Suspicious. Seven receiver regressions passed after correcting an erroneous UUID-only event_id check in the QA receiver; the SDK already accepted opaque IDs. A fresh native Codex OAuth login succeeded in the user's browser.
One earlier browser identification remained unavailable in History and awaits the developer's production log search. No cause is attributed to the SDK without that evidence. Public registry installation is still pending SDK publication.