[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-datadog-v2-openapi-2026-06-22-repository-id-removed-from-required-fields-deprecated-in":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},"01KVQK8JPGV3MPXGGX1V9AX3BC","2026-06-22-repository-id-removed-from-required-fields-deprecated-in","Breaking","repository_id removed from required fields; deprecated in favor of repository_url","**`repository_id`** has been deprecated and replaced by the new **`repository_url`** field in both `BranchCoverageSummaryRequestData` and `CommitCoverageSummaryRequestData`. Critically, `repository_id` has been **removed from the `required` array** in both schemas — clients that only send `repository_id` (without `repository_url`) may still work today, but the intent is to migrate to `repository_url`. The removal of `repository_id` as a required field is a schema contract change, and clients that relied on the required constraint for validation or code generation will see a difference. The new `repository_url` field accepts full URLs with or without a scheme.","2026-06-22T12:00:42.192Z"]