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

New fields added in schema API_Entities_GeoNodeStatus: [issuable_metric_image_uploads_registry_count issuable_metric_image_uploads_synced_in_percentage issuable…

New fields added in schema API_Entities_GeoNodeStatus: [issuable_metric_image_uploads_registry_count issuable_metric_image_uploads_synced_in_percentage issuable_metric_image_uploads_verified_in_percentage issuable_metric_image_uploads_checksum_failed_count issuable_metric_image_uploads_count issuable_metric_image_uploads_failed_count issuable_metric_image_uploads_verification_failed_count issuable_metric_image_uploads_checksummed_count issuable_metric_image_uploads_verified_count issuable_metric_image_uploads_synced_count issuable_metric_image_uploads_verification_total_count issuable_metric_image_uploads_checksum_total_count issuable_metric_image_uploads_oldest_unsynced_time]

Affected surface
schema API_Entities_GeoNodeStatus
Affected field
API_Entities_GeoNodeStatus

What changed

New fields added in schema API_Entities_GeoNodeStatus: [issuable_metric_image_uploads_registry_count issuable_metric_image_uploads_synced_in_percentage issuable_metric_image_uploads_verified_in_percentage issuable_metric_image_uploads_checksum_failed_count issuable_metric_image_uploads_count issuable_metric_image_uploads_failed_count issuable_metric_image_uploads_verification_failed_count issuable_metric_image_uploads_checksummed_count issuable_metric_image_uploads_verified_count issuable_metric_image_uploads_synced_count issuable_metric_image_uploads_verification_total_count issuable_metric_image_uploads_checksum_total_count issuable_metric_image_uploads_oldest_unsynced_time] Affected surface: schema API_Entities_GeoNodeStatus. Root cause: schema `API_Entities_GeoNodeStatus`. Detected at Thu, 21 May 2026 04:23:23 UTC UTC.

Diff

{
  "added_fields": [
    "issuable_metric_image_uploads_registry_count",
    "issuable_metric_image_uploads_synced_in_percentage",
    "issuable_metric_image_uploads_verified_in_percentage",
    "issuable_metric_image_uploads_checksum_failed_count",
    "issuable_metric_image_uploads_count",
    "issuable_metric_image_uploads_failed_count",
    "issuable_metric_image_uploads_verification_failed_count",
    "issuable_metric_image_uploads_checksummed_count",
    "issuable_metric_image_uploads_verified_count",
    "issuable_metric_image_uploads_synced_count",
    "issuable_metric_image_uploads_verification_total_count",
    "issuable_metric_image_uploads_checksum_total_count",
    "issuable_metric_image_uploads_oldest_unsynced_time"
  ],
  "path": "schema API_Entities_GeoNodeStatus",
  "schema_path": "schema API_Entities_GeoNodeStatus"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

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.