`Board.creator` is now nullable in API version 2027-04

The creator field on the Board object now returns User instead of User!, so it can be null. The field description now says so: "The creator of the board. Returns null if the creator can't be resolved."

Previously the schema promised that every board has a resolvable creator. When a creator could not be resolved, a non-nullable field could not return null, so the request could fail or return an error for that board. With a nullable creator, creator is null in that case and the rest of the board data is not affected by it.

This is a breaking change for clients that rely on the non-null type, for example code generated from the schema with a non-null creator, or code that reads creator.id or creator.name without checking. Treat creator as optional: check for null before reading its fields, and regenerate any schema-derived types for 2027-04.

query {
  boards(ids: [1234567890]) {
    id
    creator {
      id
      name
    }
  }
}

When the creator can't be resolved, the board is still returned and creator is null, so read creator.id and creator.name only after checking that creator is not null:

{
  "data": {
    "boards": [
      {
        "id": "1234567890",
        "creator": null
      }
    ]
  }
}

For details on the Board object, see the boards reference. For the full list of changes in each version, see the API release notes.