Datadog/incidents

2026.08.28.2

Hardened codegen: instance names sanitized against path traversal; string schema patterns emit regex validation; output schemas passthrough unknown fields.

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.2

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.2

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.25.1

Changed: Updated labels for improved extension discoverability. Added cross-cutting category labels (security, observability, finops, infrastructure, networking, compliance, devops, ai, incident-response) where applicable.

2026.08.24.1

Added: Output metadata attributes for observability.

• durationMs: Method execution duration in milliseconds.
• collectedBy: Extension name that produced the data.
• fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).

2026.08.21.2

Changed: Every Datadog API call made by this model (via the shared _lib/api.ts helper) now names the HTTP method and path in its error message, instead of a bare "Datadog API HTTP 500: ...". A failure now reads, for example, Datadog API POST /api/v2/dora/deployment failed with HTTP 500: ... rather than just the status code and response body. Network-level failures (DNS, connection reset, etc.) that previously surfaced as a raw TypeError now also say which Datadog operation was being attempted.

No changes to method arguments, resource schemas, or successful-call behavior — only error paths are affected.

2026.08.21.1

Changed: Schema-only tightening pass, no behavioral change.

• Added .min(1) to apiKey/appKey in the global arguments and to the required incident_id/impact_id UUID arguments across list_incident_impacts, create_incident_impact, and delete_incident_impact, so empty identifiers are rejected before making an API call.
• Added .describe() to the previously undocumented fields argument on create_incident_impact.

2026.07.20.11

Added: Initial code-generated release of @webframp/datadog/incidents with 3 methods covering the Datadog incidents API surface.