diff --git a/client-sdks/advanced/attachments.mdx b/client-sdks/advanced/attachments.mdx
index 529b5db0..552b0100 100644
--- a/client-sdks/advanced/attachments.mdx
+++ b/client-sdks/advanced/attachments.mdx
@@ -2149,7 +2149,7 @@ var queue = new AttachmentQueue(new AttachmentQueueOptions
 ### Transferring Large Files Without Buffering
 
 <Note>
-This section applies to React Native, Expo and Node.js platforms only, and requires `@powersync/react-native` v2.0.3 or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later. 
+This section applies to React Native, Expo and Node.js platforms only, and requires `@powersync/react-native` v2.1.0 or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later. 
 
 In the Dart and Kotlin SDKs, the remote storage interface is already stream-based (`Stream`/`Flow`), so transfers can avoid buffering. The Swift SDK currently receives files as `Data` and has no streaming equivalent yet.
 </Note>
@@ -2230,7 +2230,7 @@ async function attachRecording(localUri: string, recordingId: string) {
 ### Custom Transport Adapters
 
 <Note>
-The transport API requires `@powersync/web` v2.2.0, `@powersync/react-native` v2.0.3, or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later.
+The transport API requires `@powersync/web` v2.2.0, `@powersync/react-native` v2.1.0, or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later.
 </Note>
 
 In the JavaScript SDKs, you can also write your own [transport adapter](#transferring-large-files-without-buffering). A custom remote storage adapter always receives the file as one full in-memory buffer. A custom transport receives the file's path instead. This makes the following possible: