New: MCP server monitoring is live. Start free trial
StatsigSchemaBehavioral

Response schema changed for PUT /console/v1/release_pipeline_triggers/{id}/approve (ReleasePipelineTriggerResponseDto)

Affected surface
PUT /console/v1/release_pipeline_triggers/{id}/approve
Affected field
ReleasePipelineTriggerResponseDto

What changed

Response schema changed for PUT /console/v1/release_pipeline_triggers/{id}/approve (ReleasePipelineTriggerResponseDto) Affected surface: PUT /console/v1/release_pipeline_triggers/{id}/approve. Root cause: schema `ReleasePipelineTriggerResponseDto`. Detected at Mon, 27 Apr 2026 18:36:39 UTC UTC.

Diff

{
  "path": "PUT /console/v1/release_pipeline_triggers/{id}/approve",
  "removed_fields": [
    "configSnapshotID"
  ],
  "schema_path": "schema ReleasePipelineTriggerResponseDto"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.