pydantic ValidationError on files.list() means the API shape changed; upgrade the client

The root cause was in the OpenAPI spec, not your code: the permissions field changed shape (from a list of string ids to a list of objects) and the generated SDK's parsing model rejected real responses. Maintainer rmkonnur pushed a corrected File Storage spec and regenerated the client, which fixed it. Takeaways: (1) upgrade merge-python-client to the latest release when you hit pydantic ValidationError on list() calls, spec drift is the usual culprit; (2) if you cannot upgrade, skip the SDK and call the REST endpoint directly (GET https://api.merge.dev/api/filestorage/v1/files with your API key and account token headers) and parse the JSON yourself.

Asked in GitHub issue gh:merge-api/merge-python-client#38: Issue merge-api/merge-python-client#38 (closed, 11 comments): reporter got pydantic.error_wrappers.ValidationError from client.filestorage.files.list() on code that used to work, suspecting a server-side JSON change the SDK did not reflect. The verified fix/answer: The root cause was in the OpenAPI spec, not your code: the permissions field changed shape (from a list of string ids to a list of objects) and the generated SDK's parsing model rejected real responses. Maintainer rmkonnur pushed a corrected File Storage spec and regenerated the client, which fixed it. Takeaways: (1) upgrade merge-python-client to the latest release when you hit pydantic ValidationError on list() calls, spec drift is the usual culprit; (2) if you cannot upgrade, skip the SDK and call the REST endpoint directly (GET https://api.merge.dev/api/filestorage/v1/files with your API key and account token headers) and parse the JSON yourself. Source: https://github.com/merge-api/merge-python-client/issues/38