New fields added in schema API_Entities_GeoNodeStatus: [vulnerability_export_part_uploads_verification_failed_count vulnerability_export_part_uploads_checksumme…

What changed

New fields added in schema API_Entities_GeoNodeStatus: [vulnerability_export_part_uploads_verification_failed_count vulnerability_export_part_uploads_checksummed_count vulnerability_export_part_uploads_verification_total_count vulnerability_export_part_uploads_synced_in_percentage vulnerability_export_part_uploads_checksum_total_count vulnerability_export_part_uploads_registry_count vulnerability_export_part_uploads_count vulnerability_export_part_uploads_verified_count vulnerability_export_part_uploads_checksum_failed_count vulnerability_export_part_uploads_verified_in_percentage vulnerability_export_part_uploads_failed_count vulnerability_export_part_uploads_synced_count vulnerability_export_part_uploads_oldest_unsynced_time] Affected surface: schema API_Entities_GeoNodeStatus. Root cause: schema `API_Entities_GeoNodeStatus`. Detected at Wed, 27 May 2026 17:47:29 UTC UTC.

Diff

{
  "added_fields": [
    "vulnerability_export_part_uploads_verification_failed_count",
    "vulnerability_export_part_uploads_checksummed_count",
    "vulnerability_export_part_uploads_verification_total_count",
    "vulnerability_export_part_uploads_synced_in_percentage",
    "vulnerability_export_part_uploads_checksum_total_count",
    "vulnerability_export_part_uploads_registry_count",
    "vulnerability_export_part_uploads_count",
    "vulnerability_export_part_uploads_verified_count",
    "vulnerability_export_part_uploads_checksum_failed_count",
    "vulnerability_export_part_uploads_verified_in_percentage",
    "vulnerability_export_part_uploads_failed_count",
    "vulnerability_export_part_uploads_synced_count",
    "vulnerability_export_part_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.

Recommended action

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