[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-datadog-v2-openapi-2026-06-29-ciapppipelineeventjob-schema-restructured-finishedpipeline":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"datadog-v2-openapi","Datadog API v2","datadog","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FDataDog\u002Fdatadog-api-client-typescript\u002Fmaster\u002F.generator\u002Fschemas\u002Fv2\u002Fopenapi.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KW96A6AHF5VHSSN9GW7P681P","2026-06-29-ciapppipelineeventjob-schema-restructured-finishedpipeline","Breaking","CIAppPipelineEventJob schema restructured; FinishedPipeline required field added","Several breaking changes to CI App pipeline event schemas:\n\n- **`CIAppPipelineEventJob`** was previously a concrete object schema; it is now a `oneOf` union of `CIAppPipelineEventFinishedJob` and `CIAppPipelineEventInProgressJob`. Clients that previously used the flat schema will need to handle both variants.\n- **`CIAppPipelineEventFinishedPipeline`** gains a new **required** field `end`, which was previously already present but not listed as required — clients sending pipeline-finished events that omit `end` will now be rejected.\n- **`CIAppPipelineEventFinishedJob`** (new schema, extracted from the old `CIAppPipelineEventJob`) changes required fields: `unique_id` → `id`, and adds `pipeline_unique_id` and `pipeline_name` as required; removes `partial_retry` as required.\n- **`CIAppPipelineEventInProgressJob`** (new schema, extracted from the old `CIAppPipelineEventJob`) changes its `status` reference from `CIAppPipelineEventJobStatus` to the new `CIAppPipelineEventJobInProgressStatus` (enum `[\"running\"]`), and drops `end` from required fields.\n- New schema **`CIAppPipelineEventJobInProgressStatus`** added with enum value `running`.","2026-06-29T08:00:43.345Z"]