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

New fields added in schema API_Entities_GeoNodeStatus: [packages_debian_project_component_files_count packages_debian_project_component_files_verification_faile…

New fields added in schema API_Entities_GeoNodeStatus: [packages_debian_project_component_files_count packages_debian_project_component_files_verification_failed_count packages_debian_project_component_files_verified_count packages_debian_project_component_files_synced_count packages_debian_project_component_files_failed_count packages_debian_project_component_files_checksum_failed_count packages_debian_project_component_files_checksummed_count packages_debian_project_component_files_synced_in_percentage packages_debian_project_component_files_verification_total_count packages_debian_project_component_files_verified_in_percentage packages_debian_project_component_files_registry_count packages_debian_project_component_files_checksum_total_count packages_debian_project_component_files_oldest_unsynced_time]

Affected surface
schema API_Entities_GeoNodeStatus
Affected field
API_Entities_GeoNodeStatus

What changed

New fields added in schema API_Entities_GeoNodeStatus: [packages_debian_project_component_files_count packages_debian_project_component_files_verification_failed_count packages_debian_project_component_files_verified_count packages_debian_project_component_files_synced_count packages_debian_project_component_files_failed_count packages_debian_project_component_files_checksum_failed_count packages_debian_project_component_files_checksummed_count packages_debian_project_component_files_synced_in_percentage packages_debian_project_component_files_verification_total_count packages_debian_project_component_files_verified_in_percentage packages_debian_project_component_files_registry_count packages_debian_project_component_files_checksum_total_count packages_debian_project_component_files_oldest_unsynced_time] Affected surface: schema API_Entities_GeoNodeStatus. Root cause: schema `API_Entities_GeoNodeStatus`. Detected at Mon, 25 May 2026 17:24:38 UTC UTC.

Diff

{
  "added_fields": [
    "packages_debian_project_component_files_count",
    "packages_debian_project_component_files_verification_failed_count",
    "packages_debian_project_component_files_verified_count",
    "packages_debian_project_component_files_synced_count",
    "packages_debian_project_component_files_failed_count",
    "packages_debian_project_component_files_checksum_failed_count",
    "packages_debian_project_component_files_checksummed_count",
    "packages_debian_project_component_files_synced_in_percentage",
    "packages_debian_project_component_files_verification_total_count",
    "packages_debian_project_component_files_verified_in_percentage",
    "packages_debian_project_component_files_registry_count",
    "packages_debian_project_component_files_checksum_total_count",
    "packages_debian_project_component_files_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.