`Asset.uploaded_by` is now nullable in API version 2027-04

The uploaded_by field on the Asset object now returns User instead of User!, so it can be null. The field description now says so: "The user who uploaded the file. Returns null if the uploader can't be resolved."

Previously the schema promised that every asset has a resolvable uploader. With a nullable uploaded_by, an asset whose uploader can't be resolved is returned with uploaded_by set to null.

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 uploaded_by, or code that reads uploaded_by.id or uploaded_by.name without checking. Treat uploaded_by as optional: check for null before reading its fields, and regenerate any schema-derived types for 2027-04.

query {
  assets(ids: [1234567890]) {
    id
    # uploaded_by can be null when the uploader can't be resolved
    uploaded_by {
      id
      name
    }
  }
}

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