Hotfix: Updates returned in reverse chronological order

We recently fixed a bug that caused updates to be returned in chronological order (oldest first) instead of reverse chronological order (newest first) when queried through items. This bug impacted API versions 2024-10 and later.

The fix was deployed, and updates should now be returned in reverse chronological order.

query {
  items (ids: 123456890) {
    updates {
      id
      created_at
    }
  }
}