chore(deps): bump hotdata from 0.11.0 to 0.12.0

[dependabot]

Bumps hotdata from 0.11.0 to 0.12.0.

Release notes

Sourced from hotdata's releases.

hotdata 0.12.0

Added

• hotdata.Configuration reads HOTDATA_API_KEY, HOTDATA_WORKSPACE and HOTDATA_API_URL from the environment when api_key, workspace_id or host is not passed, matching the CLI. Explicit arguments always win and an empty variable counts as unset.
• A workspace-scoped call made with no workspace id configured now raises hotdata.MissingWorkspaceError (an ApiValueError) before anything is sent, naming workspace_id= and HOTDATA_WORKSPACE. Previously the request went out without X-Workspace-Id and the server answered a bare 404. Calls that pass the header via _headers, use _request_auth, or target endpoints that are not workspace-scoped (the Workspaces endpoints) are unaffected.
• QueryApi.fetch_ready_result(result_id, x_database_id, offset=, limit=, format=) waits for a result to be ready and then fetches its rows in one call. QueryApi.wait_for_result is unchanged: it polls with limit=0 and returns a status-only response with no rows, which its docstring now states up front.
• DatabasesApi.load_database_table and ConnectionsApi.load_managed_table (the classes exported from hotdata) retry automatically while another load holds the table: HTTP 409 with error code RESOURCE_LOCKED is retried, honouring Retry-After (else exponential backoff) with jitter, under a 60s budget by default. Tune or disable with LoadRetryPolicy (DatabasesApi(client, load_retry=LoadRetryPolicy(...))); when the budget runs out, hotdata.TableLockedError (a 409 ApiException) is raised. Other 409s (CONFLICT, IDEMPOTENCY_KEY_CONFLICT) are never retried. The raw generated classes stay available under hotdata.api.*.

Changed

• Breaking: request models reject unknown fields. Every model used as a request body (QueryRequest, LoadManagedTableRequest, CreateDatabaseRequest, ... and the models nested in them) now carries extra="forbid", so a misspelled keyword, or a field a newer API has that this SDK release does not know yet, raises pydantic.ValidationError at construction instead of being silently dropped from the request. Upgrade the SDK to use a new field. Response models are unchanged: unknown fields in server responses are still ignored, so a newer server never breaks an older SDK.
• feat(query): add arrow ipc stream response format
• chore(query): clarify write statement handling in dialect parameter
• chore(indexes): clarify vector index constraints and algorithms
• chore(indexes): clarify vector precision documentation
• chore: clarify sorted table and index creation constraints
• feat(indexes): add nlist field to index responses
• chore(uploads): clarify finalized upload retention period
• chore(loads): clarify idempotency key conflict behavior
• chore(uploads): clarify finalize token validation errors
• feat(jobs): add ivf_index_hold job type support
• feat(indexes): add algorithm and probe_fraction support

... (truncated)

Changelog

Sourced from hotdata's changelog.

[0.12.0] - 2026-10-15

Added

• hotdata.Configuration reads HOTDATA_API_KEY, HOTDATA_WORKSPACE and HOTDATA_API_URL from the environment when api_key, workspace_id or host is not passed, matching the CLI. Explicit arguments always win and an empty variable counts as unset.
• A workspace-scoped call made with no workspace id configured now raises hotdata.MissingWorkspaceError (an ApiValueError) before anything is sent, naming workspace_id= and HOTDATA_WORKSPACE. Previously the request went out without X-Workspace-Id and the server answered a bare 404. Calls that pass the header via _headers, use _request_auth, or target endpoints that are not workspace-scoped (the Workspaces endpoints) are unaffected.
• QueryApi.fetch_ready_result(result_id, x_database_id, offset=, limit=, format=) waits for a result to be ready and then fetches its rows in one call. QueryApi.wait_for_result is unchanged: it polls with limit=0 and returns a status-only response with no rows, which its docstring now states up front.
• DatabasesApi.load_database_table and ConnectionsApi.load_managed_table (the classes exported from hotdata) retry automatically while another load holds the table: HTTP 409 with error code RESOURCE_LOCKED is retried, honouring Retry-After (else exponential backoff) with jitter, under a 60s budget by default. Tune or disable with LoadRetryPolicy (DatabasesApi(client, load_retry=LoadRetryPolicy(...))); when the budget runs out, hotdata.TableLockedError (a 409 ApiException) is raised. Other 409s (CONFLICT, IDEMPOTENCY_KEY_CONFLICT) are never retried. The raw generated classes stay available under hotdata.api.*.

Changed

• Breaking: request models reject unknown fields. Every model used as a request body (QueryRequest, LoadManagedTableRequest, CreateDatabaseRequest, ... and the models nested in them) now carries extra="forbid", so a misspelled keyword, or a field a newer API has that this SDK release does not know yet, raises pydantic.ValidationError at construction instead of being silently dropped from the request. Upgrade the SDK to use a new field. Response models are unchanged: unknown fields in server responses are still ignored, so a newer server never breaks an older SDK.
• feat(query): add arrow ipc stream response format
• chore(query): clarify write statement handling in dialect parameter
• chore(indexes): clarify vector index constraints and algorithms
• chore(indexes): clarify vector precision documentation
• chore: clarify sorted table and index creation constraints
• feat(indexes): add nlist field to index responses
• chore(uploads): clarify finalized upload retention period
• chore(loads): clarify idempotency key conflict behavior
• chore(uploads): clarify finalize token validation errors
• feat(jobs): add ivf_index_hold job type support

... (truncated)

Commits

• 36fbe60 chore: release v0.12.0 (#220)
• 3373899 feat: retry locked loads, read env vars, clear workspace error (#219)
• 84cf4b9 ci: set origin/HEAD before running release.sh (#218)
• f1fd013 ci: cut releases from a workflow that runs release.sh (#217)
• e6f00ff feat(query): add arrow ipc stream response format (#216)
• 716b0dd chore(query): clarify write statement handling in dialect parameter (#213)
• ae1c7b8 chore(indexes): clarify vector index constraints and algorithms (#212)
• 43afdb4 chore(indexes): clarify vector precision documentation (#211)
• 8a9d9f9 chore: clarify sorted table and index creation constraints (#209)
• cf1f82b feat(indexes): add nlist field to index responses (#208)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)