---
changelog:
  category: Release
  version: files-sdk@3.2.1
date: '2026-11-22T04:15:52Z'
seo:
  description: >-
    Stop the Appwrite adapter (files-sdk/appwrite) from following redirects on
    resumable-upload chunk requests. Those chunks are sent with fetch and carry
    the API…
title: files-sdk@3.2.1
type: changelog
---
## Patch Changes

- 633dbb1: Stop the Appwrite adapter (`files-sdk/appwrite`) from following redirects on resumable-upload chunk requests. Those chunks are sent with `fetch` and carry the API key in a header, so a redirect from the configured `endpoint` re-sent the key to whatever host it named. A redirected chunk now fails with a `Provider` error, on every supported `node-appwrite` version, matching what the SDK itself does for its own calls from 31.1.
- 633dbb1: Accept `node-appwrite` 30, 31, and 32 as peers of the Appwrite adapter (`files-sdk/appwrite`). The Storage API the adapter calls is unchanged across all three majors. One behaviour to know about comes from the SDK itself: from `node-appwrite` 31.1 every call refuses to follow an HTTP redirect, so an `endpoint` that redirects (an `http://` URL that upgrades to `https://`, say) now fails with a `Provider` error naming the redirect instead of being followed. Point `endpoint` at the final URL.
- 633dbb1: Document and test `upload()` and `download()` in Convex mutations for the Convex adapter (`files-sdk/convex`). Convex 1.48 added `ctx.storage.store()` and `ctx.storage.get()` to mutations, and the adapter feature-detects them, so both verbs already work there on 1.48 and later (the bytes count toward the mutation's transaction limits). The `Unsupported` error thrown where they are missing (queries, and mutations on older Convex) now says so instead of claiming they need an action. No peer range change.
- 633dbb1: Reject keys containing a line break in the FTP adapter (`files-sdk/ftp`) with an `Invalid` error before any command is sent. FTP commands are single lines, so a CR or LF in a path can't be sent, and `basic-ftp` handled that badly: before 6.2.3 a ranged `download()` of such a key threw an uncaught exception from inside a socket handler, and newer versions reject with a retryable `Provider` error that still closes an injected client's connection. Every supported `basic-ftp` version now fails the same deterministic way.
- 633dbb1: Accept `@googleapis/drive` 27 as a peer of the Google Drive adapter (`files-sdk/google-drive`). The Drive v3 client the adapter calls is identical to 26's; the release only adds a field to an approvals type.
- 633dbb1: Keep a throttled, failing, or unreachable Microsoft Entra token endpoint a retryable `Provider` error in the OneDrive and SharePoint adapters (`files-sdk/onedrive`, `files-sdk/sharepoint`) when authenticating with `clientCredentials`. `@azure/identity` reports every failed token request the same way, so a `503` from the token endpoint surfaced as `Unauthorized`: never retried, and never failed over by `failover()`. With `@azure/identity` 4.14 or later the error names its cause, and the adapter now reports a `429`, a `5xx`, or a network failure as `Provider`, as the `oauth` refresh-token flow already did. A rejected client secret is still `Unauthorized`, and older `@azure/identity` versions behave as before. No peer range change.
- 633dbb1: Accept `pocketbase` 0.29 as a peer of the PocketBase adapter (`files-sdk/pocketbase`). The record and file APIs the adapter uses are unchanged. The SDK now clears its auth store when a request answers `401`: with credentials the adapter manages, the next call logs in again rather than failing until the token expires locally; with your own `client`, a `401` on an adapter request signs that shared client out too (call `client.autoClearAuthStore(false)` to opt out).
- 633dbb1: Reject keys with a `.` or `..` path segment in the Supabase adapter (`files-sdk/supabase`) with an `Invalid` error before any request. The adapter builds its own request URLs for `upload`, `download`, `head`, `exists`, `url`, and `signedUploadUrl`, and a URL resolves those segments, so `a/../b.txt` silently addressed `b.txt`, `../other-bucket/x` reached another bucket, and enough `..` segments left the Storage API altogether, each time with the client's credentials attached. `@supabase/storage-js` 2.119.2 added the same refusal to its own requests; the adapter's requests don't pass through it. If you hand caller-supplied keys to a Supabase-backed `Files` instance, upgrade.
- 1906dba: Fix private downloads in the Vercel Blob adapter (`files-sdk/vercel-blob`) for keys containing `#`, `?`, or `%`. `download()` handed the raw key to `@vercel/blob`'s `get()`, which builds the blob URL by plain concatenation, so a `#` or `?` ended the path there and a `%xx` sequence was decoded: `reports/Invoice #42.pdf` read whatever blob sat at `reports/Invoice ` (or failed with `NotFound`), while `head()` still reported the right blob's metadata. The download now reads the blob's own URL, the one `head()` returns, as public downloads already do. Keys with only spaces or non-ASCII characters were not affected, and public stores never were.
- 1906dba: Refuse private `url()` in the Vercel Blob adapter (`files-sdk/vercel-blob`) for keys a presigned URL can't carry, with an `Unsupported` error before any token is issued. `@vercel/blob` puts the key into the presigned `GET` URL unencoded, so a `#`, `?`, `%`, `\`, a `.` or `..` path segment, or a trailing space produced a link to a different path than the one signed (`reports/Invoice #42.pdf` became a link to `reports/Invoice `), and a key starting with `http://` or `https://` produced a signed link to that other host. `download()` reads those blobs correctly, and a gateway in `auto` download mode proxies them instead of redirecting. Public stores are unaffected: their URLs encode the key.
