Skip to content

fix(webhooks): make client_identity optional and nullable throughout - #23

Merged
KonstantinSerebryakov merged 1 commit into
mainfrom
fix/webhook-nullable-client-identity
Oct 8, 2026
Merged

KonstantinSerebryakov merged 1 commit into
mainfrom
fix/webhook-nullable-client-identity

Conversation

@KonstantinSerebryakov

Copy link
Copy Markdown
Contributor

Webhook receivers must not depend on client attribution being available or complete. client_identity now accepts omission or null, and every nested field is optional and nullable, including fields inside claims, verified, assessments and evidence.

A dedicated WebhookClientIdentity schema documents this best-effort contract without relaxing the stored identity model used by other API surfaces. Known non-null values keep their type validation. Distribution schemas are rebuilt; Core emission does not need to change because its existing output remains valid.

Validation: npm run bundle, npm run lint, npm test (76 passing). Regression checks missing/null object, empty object, null nested fields and partial array items; invalid non-null types remain rejected.

@KonstantinSerebryakov
KonstantinSerebryakov merged commit b568f33 into main Oct 8, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant