Falai/compute

2026.10.14.1

Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.

Upgrade note: Metadata only. No code, schema, or behavioral changes.

2026.10.07.1

Fixed: A stalled fal.ai request no longer hangs the method. Every request now has a 60-second deadline that covers the response body, and a timeout raises an error naming the HTTP method and URL.

Fixed: An empty 2xx response body (such as a 202 or 204) is handled explicitly. Paginated list calls treat it as an empty page instead of failing with a bare SyntaxError. Methods that must return data (get, create, update, and unpaginated list) raise an error naming the HTTP method and path instead of failing later with a TypeError. Delete and action methods still accept an empty body. A malformed JSON body now raises an error that names the HTTP method, path, and status code.

Changed: A Retry-After header on a 429 response is capped at 30 seconds per retry, so a large value can no longer stall a call for minutes. Retry count is unchanged.

No methods, arguments, or resource schemas changed. Apart from the hardening above, behavior is the same as the previous version.

2026.09.18.1

Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the repo. No behavioral changes in this extension.

2026.09.17.2

BREAKING: fal.ai removed the create_compute_instance operation (POST /compute/instances) — instances can no longer be created through this API. Add get_compute_instance (GET /compute/instances/{id}). Callers relying on create_compute_instance must provision instances another way; there is no in-place migration for this removal. Also: response schema fields are now generated as optional/nullable-optional regardless of the spec's required list, so reading a resource stored under an older model version no longer throws when the live API has since added required fields.

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.09.10.4

Fixed:

• Resource instance names for get/update methods with two or more path parameters (e.g. get_app_queue_info(owner, name), get_workflow(username, workflow_name)) were built by joining raw values with "_". Two distinct owner/name pairs that split differently around an underscore (e.g. "john"/"doe_app" and "john_doe"/"app") produced the identical instance name and collided. Multi-param instance names are now derived from a hash of the JSON-encoded parameter tuple, which delimits each part unambiguously.

Upgrade note: No schema changes. All fixes are internal to method execution; existing stored resources are unaffected.

2026.09.10.4

Fixed:

• Resource instance names for get/update methods with two or more path parameters (e.g. get_app_queue_info(owner, name), get_workflow(username, workflow_name)) were built by joining raw values with "_". Two distinct owner/name pairs that split differently around an underscore (e.g. "john"/"doe_app" and "john_doe"/"app") produced the identical instance name and collided. Multi-param instance names are now derived from a hash of the JSON-encoded parameter tuple, which delimits each part unambiguously.

Upgrade note: No schema changes. All fixes are internal to method execution; existing stored resources are unaffected.