Breaking Change: Release 2025.52

1 min read

With release 2025.52 our internal GraphQL API will have some breaking changes due to the upgrade of our DB ORM packages, which brought significant performance improvements.

Timeline

• Expected release date: January 7, 2026

What's changing

For some models/fields, the orderBy input shape has changed. Sorting on nullable/optional fields now requires a nested object format.

What error will I see?

If you use the old format for affected fields, requests will fail with:

Variable "$orderBy" got invalid value "asc" at "orderBy.firstName";
Expected type "SortOrderInput" to be an object.

Migration

• Before:

orderBy: [{ firstName: asc }]

• After:

orderBy: [{ firstName: { sort: asc } }]

Which fields are NOT affected?

Required fields (non-nullable) still use the old format:

• createdAt, updatedAt — can still use orderBy: [{ createdAt: asc }]
• id, email (on most models)
• name (on most models)

Only nullable fields (marked with ? in our db model) require the new format.

Testing

1. Identify queries/mutations that use orderBy
2. Check if you're sorting on nullable fields (see list below)
3. Update to use { sort: <direction> } format
4. Test in [staging environment if available]

| Author | |