[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-vercel-changelog-2026-05-19-new-required-field-justification-added-to-firewall-event":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"vercel-changelog","Vercel API","vercel","openapi-json","rest","https:\u002F\u002Fopenapi.vercel.sh\u002F",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KRYRHJC94XJBZP3KJSYTQZ9H","2026-05-19-new-required-field-justification-added-to-firewall-event","Breaking","New required field `justification` added to firewall event response objects","A new `justification` field (type `string`) has been added to **three** firewall\u002FWAF-related response object schemas, and in all three cases it is listed as **required**. Clients that deserialize these responses into strict models (e.g. generated SDKs, TypeScript types, Zod schemas) may break if they don't expect this field. Note: in the third schema variant `justification` is `nullable: true`, which slightly softens the impact there.","2026-05-19T00:00:35.209Z"]