chore: remove files endpoints in favor of uploads

.openapi-generator/FILES

@@ -87,7 +87,6 @@ docs/ListResultsResponse.md
 docs/ListSavedQueriesResponse.md
 docs/ListSavedQueryVersionsResponse.md
 docs/ListSecretsResponse.md
-docs/ListUploadsResponse.md
 docs/ListWorkspacesResponse.md
 docs/LoadManagedTableRequest.md
 docs/LoadManagedTableResponse.md
@@ -128,8 +127,6 @@ docs/UpdateEmbeddingProviderResponse.md
 docs/UpdateSavedQueryRequest.md
 docs/UpdateSecretRequest.md
 docs/UpdateSecretResponse.md
-docs/UploadInfo.md
-docs/UploadResponse.md
 docs/UploadSessionResponse.md
 docs/UploadsApi.md
 docs/UpsertDatabaseContextRequest.md
@@ -241,7 +238,6 @@ hotdata/models/list_results_response.py
 hotdata/models/list_saved_queries_response.py
 hotdata/models/list_saved_query_versions_response.py
 hotdata/models/list_secrets_response.py
-hotdata/models/list_uploads_response.py
 hotdata/models/list_workspaces_response.py
 hotdata/models/load_managed_table_request.py
 hotdata/models/load_managed_table_response.py
@@ -276,8 +272,6 @@ hotdata/models/update_embedding_provider_response.py
 hotdata/models/update_saved_query_request.py
 hotdata/models/update_secret_request.py
 hotdata/models/update_secret_response.py
-hotdata/models/upload_info.py
-hotdata/models/upload_response.py
 hotdata/models/upload_session_response.py
 hotdata/models/upsert_database_context_request.py
 hotdata/models/upsert_database_context_response.py
@@ -374,7 +368,6 @@ test/test_list_results_response.py
 test/test_list_saved_queries_response.py
 test/test_list_saved_query_versions_response.py
 test/test_list_secrets_response.py
-test/test_list_uploads_response.py
 test/test_list_workspaces_response.py
 test/test_load_managed_table_request.py
 test/test_load_managed_table_response.py
@@ -415,8 +408,6 @@ test/test_update_embedding_provider_response.py
 test/test_update_saved_query_request.py
 test/test_update_secret_request.py
 test/test_update_secret_response.py
-test/test_upload_info.py
-test/test_upload_response.py
 test/test_upload_session_response.py
 test/test_uploads_api.py
 test/test_upsert_database_context_request.py

CHANGELOG.md

@@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Removed
+
+- The legacy `POST /v1/files` upload endpoints have been removed in favor of the
+  presigned upload flow. This drops `hotdata.UploadsApi.upload_stream`, the raw
+  `upload_file(body=...)` / `list_uploads` operations, and the `UploadResponse`,
+  `UploadInfo`, and `ListUploadsResponse` models. Use
+  `hotdata.UploadsApi.upload_file(source, ...)` (direct-to-storage) instead.
+
 ## [0.8.0] - 2026-07-20
 
 ### Changed

README.md

@@ -156,20 +156,6 @@ Pass a `threading.Event` as `cancel_event` to abort an in-flight upload; tune th
 control-plane calls with `request_timeout` (storage-PUT timeouts are automatic and
 size-scaled).
 
-For that fallback (or to upload from a non-seekable stream), use `upload_stream`,
-which sends the bytes to the legacy `POST /v1/files` endpoint in one request,
-streaming a file object without buffering it in memory:
-
-```python
-with open("data.parquet", "rb") as f:
-    resp = uploads.upload_stream(f, content_type="application/parquet")
-print(resp.id)
-```
-
-Note `upload_file` shadows the generated raw-body `upload_file(body=...)`; that
-raw operation is still reachable at
-`hotdata.api.uploads_api.UploadsApi.upload_file`.
-
 ## API reference
 
 Generated Markdown for every operation and model is in [`docs/`](https://github.com/hotdata-dev/sdk-python/tree/main/docs):

docs/LoadManagedTableRequest.md

@@ -12,7 +12,7 @@ Name | Type | Description | Notes
 **key** | **List[str]** | Key columns identifying rows for `\"delete\"`, `\"update\"`, and `\"upsert\"` loads — the columns whose values decide which existing row an incoming row removes, updates, or replaces. Omit to use the key the table was created with. Keep the key consistent across loads of the same table: changing it re-targets which rows are matched. Ignored for `\"replace\"` and `\"append\"`. | [optional] 
 **mode** | **str** | How the data is applied: `\"replace\"` overwrites the table's contents, `\"append\"` inserts the new rows on top of the existing data. | 
 **result_id** | **str** | ID of a persisted query result (see `GET /v1/results/{result_id}`) to publish as the table's contents. The result is copied into the table, so the table keeps its data even after the result expires. A result can be loaded into any number of tables. Provide either this or `upload_id`, not both. | [optional] 
-**upload_id** | **str** | ID of a previously-staged upload (see `POST /v1/files`). The upload is claimed atomically; concurrent loads against the same `upload_id` return 409. Provide either this or `result_id`, not both. | [optional] 
+**upload_id** | **str** | ID of a previously-staged upload (see `POST /v1/uploads`). The upload is claimed atomically; concurrent loads against the same `upload_id` return 409. Provide either this or `result_id`, not both. | [optional] 
 
 ## Example